Triple
T4455748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balikh River |
E97716
|
entity |
| Predicate | crossesBorderFrom |
P13760
|
FINISHED |
| Object | Turkey to Syria |
—
|
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: Turkey to Syria | Statement: [Balikh River, crossesBorderFrom, Turkey to Syria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesBorderFrom Context triple: [Balikh River, crossesBorderFrom, Turkey to Syria]
-
A.
crossesBorderOf
chosen
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
B.
hasBorderCrossing
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
-
C.
crossesStateBoundaryViaBridgeTo
Indicates that one entity crosses a state boundary to reach another entity specifically by traveling over a bridge.
-
D.
nearBorderCrossing
Indicates that an entity is located close to a border crossing point between two regions or countries.
-
E.
crossesRegion
Indicates that an entity moves through or passes across the spatial extent of a specified region.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355f79ca481909338dda9f4f7171f |
completed | March 13, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.