Triple
T24845902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Rift Valley |
E621744
|
entity |
| Predicate | majorHomininSite |
P108844
|
FINISHED |
| Object | Koobi Fora |
—
|
NE NERFINISHED |
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: Koobi Fora | Statement: [Great Rift Valley, majorHomininSite, Koobi Fora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorHomininSite Context triple: [Great Rift Valley, majorHomininSite, Koobi Fora]
-
A.
fossilSiteType
Indicates the specific type or classification of a site where fossils are found or collected.
-
B.
notableArchaeologicalSite
Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
-
C.
hasArchaeologicalSiteIn
chosen
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
D.
modernArchaeologicalSite
Indicates that a location functions as an archaeological site characterized by modern-era remains, research, or excavation activities.
-
E.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 5:19 a.m.