Triple
T30886157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuqat al Khams District |
E786770
|
entity |
| Predicate | borderCrossingWithTunisia |
P83182
|
FINISHED |
| Object | Ras Ajdir border crossing |
—
|
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: Ras Ajdir border crossing | Statement: [Nuqat al Khams District, borderCrossingWithTunisia, Ras Ajdir border crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingWithTunisia Context triple: [Nuqat al Khams District, borderCrossingWithTunisia, Ras Ajdir border crossing]
-
A.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
-
B.
borderTownAcrossBorder
Indicates that a town lies on one side of a border directly opposite or adjacent to a town on the other side of that border.
-
C.
borderCrossingNameInArabic
Indicates the Arabic-language name assigned to a specific border crossing.
-
D.
usesBorderCrossing
chosen
Indicates that one entity makes use of a specific border crossing point to pass from one jurisdiction or territory to another.
-
E.
distanceToTunisia
Indicates the measured or calculated distance between a given entity’s location and the country of Tunisia.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: April 29, 2026, 8:49 p.m.