Triple
T30096137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mammoth skeleton (Vika) |
E764868
|
entity |
| Predicate | taxonCommonName |
P168444
|
FINISHED |
| Object | steppe mammoth |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: steppe mammoth | Statement: [mammoth skeleton (Vika), taxonCommonName, steppe mammoth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonCommonName Context triple: [mammoth skeleton (Vika), taxonCommonName, steppe mammoth]
-
A.
describedTaxonCommonName
Indicates that a taxon is being described or referenced using its common (vernacular) name rather than its scientific name.
-
B.
subspeciesCommonName
Indicates the common (non-scientific) name used to refer to a particular subspecies.
-
C.
includesSpeciesCommonName
Indicates that an entity contains or specifies the common (vernacular) name of a species.
-
D.
animalCommonNameFeatured
Indicates that a particular animal’s common (vernacular) name is prominently highlighted or used as the primary displayed name in a given context.
-
E.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d90de4881909fa48ca060068046 |
completed | May 2, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:07 p.m.