Triple
T30760823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libya–Chad border region |
E783228
|
entity |
| Predicate | borderDelimitationBasis |
P177205
|
FINISHED |
| Object | colonial-era treaties |
—
|
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: colonial-era treaties | Statement: [Libya–Chad border region, borderDelimitationBasis, colonial-era treaties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDelimitationBasis Context triple: [Libya–Chad border region, borderDelimitationBasis, colonial-era treaties]
-
A.
basisOfBoundaries
chosen
Indicates that one entity serves as the foundational reference or criterion used to define, establish, or delimit the boundaries of another entity.
-
B.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
C.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
D.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
E.
borderCharacteristic
Indicates that one entity specifies a property, feature, or quality of the border or boundary 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: April 29, 2026, 8:39 p.m.