Triple
T21761241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quneitra |
E537166
|
entity |
| Predicate | QuneitraCrossingUsedFor |
P145260
|
FINISHED |
| Object | UN personnel movement |
—
|
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: UN personnel movement | Statement: [Quneitra, QuneitraCrossingUsedFor, UN personnel movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: QuneitraCrossingUsedFor Context triple: [Quneitra, QuneitraCrossingUsedFor, UN personnel movement]
-
A.
wasCrossroadsOf
Indicates that a place served as a central junction or meeting point where multiple routes, paths, or influences converged.
-
B.
associatedDesertRoute
Indicates a relationship where an entity is linked to, or connected with, a specific desert route, such as a path, trail, or corridor through a desert region.
-
C.
traversesDesert
Indicates that an entity moves across or through a desert region, typically implying a journey over arid terrain.
-
D.
crossesMountainPass
Indicates that an entity traverses from one side of a mountain range to another via a defined mountain pass.
-
E.
QarnAl-ManazilFor
Indicates that something is designated for, associated with, or related in purpose to Qarn Al-Manazil.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d91e9788190a11d0295306e78a4 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4c438c819089ab285e64e81d24 |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:50 p.m.