Triple
T23744031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Qaim–Abu Kamal border crossing |
E586762
|
entity |
| Predicate | nearCityInSyria |
P153530
|
FINISHED |
| Object | Abu Kamal |
—
|
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: Abu Kamal | Statement: [Al-Qaim–Abu Kamal border crossing, nearCityInSyria, Abu Kamal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearCityInSyria Context triple: [Al-Qaim–Abu Kamal border crossing, nearCityInSyria, Abu Kamal]
-
A.
distanceFromSyriaBorder
Indicates the measured spatial separation between a location and the nearest point on Syria’s national border.
-
B.
affectedSyrianRegion
Indicates that a specified Syrian region is impacted or influenced by a particular event, condition, or action.
-
C.
distanceFromDamascus
Indicates the measured distance between a given location and the city of Damascus.
-
D.
populationStatusInSyria
Indicates the status or condition of a population specifically within the geographic boundaries of Syria.
-
E.
lostLastTerritoryInSyria
Indicates that the entity ceased to control its final remaining territorial holding within Syria.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcbbcf988190b56d74af4b126bd8 |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:12 p.m.