Triple
T30760822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libya–Chad border region |
E783228
|
entity |
| Predicate | sovereigntyConfirmedFor |
P34170
|
FINISHED |
| Object | Chad |
—
|
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: Chad | Statement: [Libya–Chad border region, sovereigntyConfirmedFor, Chad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovereigntyConfirmedFor Context triple: [Libya–Chad border region, sovereigntyConfirmedFor, Chad]
-
A.
affirmsSovereigntyOf
Indicates that one entity explicitly recognizes, supports, or upholds the sovereignty or sovereign authority of another entity.
-
B.
sovereigntyHolder
Indicates which entity possesses ultimate governing authority or sovereign control over another entity or territory.
-
C.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
D.
hasSovereignAuthority
Indicates that one entity holds ultimate governing or ruling power over another entity or domain.
-
E.
recognizedAsSovereignWithin
chosen
Indicates that an entity is officially acknowledged as having sovereign authority or status within a specified domain, territory, or jurisdiction.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f9b56988190a95f2706bb6b3217 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:39 p.m.