Triple
T36620605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hala'ib Triangle |
E904025
|
entity |
| Predicate | borderRedefinedBy |
P201244
|
FINISHED |
| Object | 1902 administrative boundary |
—
|
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: 1902 administrative boundary | Statement: [Hala'ib Triangle, borderRedefinedBy, 1902 administrative boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRedefinedBy Context triple: [Hala'ib Triangle, borderRedefinedBy, 1902 administrative boundary]
-
A.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
B.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
C.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
D.
borderInternal
Indicates that one entity lies within the interior of another and shares a common boundary with it, without touching the outer boundary of the containing entity.
-
E.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
- F. None of above. chosen
Provenance (4 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
| PDg | Predicate description generation | batch_69ffe01be6e88190ac0742a5f74e769e |
completed | May 10, 2026, 1:32 a.m. |
Created at: May 3, 2026, 4:11 p.m.