Triple
T6473313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutba |
E146007
|
entity |
| Predicate | distanceFromSyriaBorder |
P71005
|
FINISHED |
| Object | approximately 160 km southeast of Syria border |
—
|
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: approximately 160 km southeast of Syria border | Statement: [Rutba, distanceFromSyriaBorder, approximately 160 km southeast of Syria border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSyriaBorder Context triple: [Rutba, distanceFromSyriaBorder, approximately 160 km southeast of Syria border]
-
A.
distanceFromBeirut
Indicates the measured spatial distance between a given entity’s location and the city of Beirut.
-
B.
distanceFromBaghdad
Indicates the spatial distance between a given location or entity and the city of Baghdad.
-
C.
distanceToRussianBorder_km
Indicates the physical distance, measured in kilometers, between a given location and the nearest point on the Russian border.
-
D.
distanceFromJerusalem
Indicates the spatial distance between a given location and Jerusalem.
-
E.
distanceToAqaba
Indicates the spatial distance between a given location and the city of Aqaba.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a32c0188190bcb3c35fc1d796a6 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067da970481908a038995ba7dfb4b |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:50 p.m.