Triple
T26714879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gürbulak |
E673522
|
entity |
| Predicate | borderCheckpointOf |
P137378
|
FINISHED |
| Object | Turkey–Iran border |
—
|
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: Turkey–Iran border | Statement: [Gürbulak, borderCheckpointOf, Turkey–Iran border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCheckpointOf Context triple: [Gürbulak, borderCheckpointOf, Turkey–Iran border]
-
A.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
-
B.
borderStationFor
chosen
Indicates that a particular border station serves, monitors, or is responsible for a specific border crossing or boundary segment.
-
C.
borderPass
Indicates that one entity crosses or moves through the boundary separating two regions or jurisdictions.
-
D.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
-
E.
borderPostName
Indicates the specific name assigned to a border post where a boundary crossing or checkpoint is located.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 27, 2026, 3:37 a.m.