Triple
T9548386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toubou people |
E230353
|
entity |
| Predicate | politicalPresence |
P84578
|
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: [Toubou people, politicalPresence, northern Chad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalPresence Context triple: [Toubou people, politicalPresence, northern Chad]
-
A.
statePartyPresence
Indicates that a particular state is formally participating in, or is a member/party to, a given agreement, event, or context.
-
B.
postPoliticalActivity
Indicates that an entity engages in political actions or activities following a particular event, period, or condition.
-
C.
representedPoliticalEntity
Indicates that one entity has served as an official political representative or agent acting on behalf of another political entity.
-
D.
politicalActivityRegion
chosen
Indicates the geographic region or area in which a political activity takes place or is focused.
-
E.
politicalSupporter
Indicates that one entity supports, endorses, or aligns with the political views, actions, or position of another entity.
- 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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99059138819088ae54b26df979cf |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:02 p.m.