Triple
T1572211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaternary period |
E33564
|
entity |
| Predicate | includesTaxonEvent |
P8809
|
FINISHED |
| Object | emergence of genus Homo |
—
|
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: emergence of genus Homo | Statement: [Quaternary period, includesTaxonEvent, emergence of genus Homo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTaxonEvent Context triple: [Quaternary period, includesTaxonEvent, emergence of genus Homo]
-
A.
includesExampleTaxon
Indicates that a taxonomic group or concept contains a specific taxon used as an illustrative or representative example.
-
B.
affectsTaxon
Indicates that one entity has an impact or influence on a particular taxon or group of organisms.
-
C.
accessionEvent
Indicates the event or process by which an item is formally acquired, accepted, or added into a collection, system, or repository.
-
D.
biogeographicEvent
chosen
Indicates an event that changes or characterizes the geographic distribution of organisms or biological communities over space and time.
-
E.
provenanceEvent
Indicates an event or action that records how an entity came to be, including its origin, creation, modification, or transfer history.
- F. None of above.
Provenance (3 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.