Triple
T30886166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuqat al Khams District |
E786770
|
entity |
| Predicate | borderDirectionRelativeToTunisia |
P197626
|
FINISHED |
| Object | east of Tunisia |
—
|
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: east of Tunisia | Statement: [Nuqat al Khams District, borderDirectionRelativeToTunisia, east of Tunisia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDirectionRelativeToTunisia Context triple: [Nuqat al Khams District, borderDirectionRelativeToTunisia, east of Tunisia]
-
A.
directionFromAlgeria
Indicates the relative compass direction in which one entity is located when viewed from Algeria.
-
B.
distanceToTunisia
Indicates the measured or calculated distance between a given entity’s location and the country of Tunisia.
-
C.
borderTypeWithAlgeria
Indicates the type or nature of the border relationship that an entity has with Algeria.
-
D.
borderDirectionRelativeToEbebiyín
Indicates the compass direction in which a given entity’s border lies relative to the location of Ebebiyín.
-
E.
directionFromLibya
Indicates the relative compass direction of one place or object as measured outward starting from Libya.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
| PDg | Predicate description generation | batch_69fe9fb88db08190a8f4af350633330e |
completed | May 9, 2026, 2:45 a.m. |
Created at: April 29, 2026, 8:49 p.m.