Triple
T34219071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadjourah Region |
E877874
|
entity |
| Predicate | historicHeartlandOf |
P126673
|
FINISHED |
| Object | Afar people |
—
|
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: Afar people | Statement: [Tadjourah Region, historicHeartlandOf, Afar people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicHeartlandOf Context triple: [Tadjourah Region, historicHeartlandOf, Afar people]
-
A.
historicalFrontier
Indicates a boundary or border that historically separated two regions, territories, or spheres of influence.
-
B.
historicalHabitat
Indicates that an entity previously lived, occurred, or was distributed within a particular habitat or environment in the past.
-
C.
historicCore
Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
-
D.
historicTerritoryLocation
Indicates that one entity is the geographical area where another entity historically held territory or exercised territorial control.
-
E.
ethnoHistoricRegion
chosen
Indicates a relationship where an entity is associated with a geographic region defined by its historical and ethnic or cultural characteristics.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
Created at: May 1, 2026, 1:55 a.m.