Triple
T31871949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tebu people |
E813627
|
entity |
| Predicate | primaryAreaInChad |
P95404
|
FINISHED |
| Object | northern Chad |
—
|
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: northern Chad | Statement: [Tebu people, primaryAreaInChad, northern Chad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAreaInChad Context triple: [Tebu people, primaryAreaInChad, northern Chad]
-
A.
primaryLocationInChad
chosen
Indicates that the referenced entity’s main or most significant location is situated within the country of Chad.
-
B.
areaRankingInChad
Indicates the relative position of an entity in a size-based ranking specifically within the geographic context of Chad.
-
C.
primaryLocationInSudan
Indicates that the primary or main location associated with an entity is situated within the country of Sudan.
-
D.
politicalStatusInChad
Indicates the political role, position, or status an entity holds within the political system or governance structure of Chad.
-
E.
demographicStatusInChad
Indicates the demographic status or characteristics of an entity within the context of Chad.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:54 p.m.