Triple
T35372986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran–Turkey border |
E1021824
|
entity |
| Predicate | borderFenceConstructionPeriod |
P126596
|
FINISHED |
| Object | 2017–2020s |
—
|
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: 2017–2020s | Statement: [Iran–Turkey border, borderFenceConstructionPeriod, 2017–2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderFenceConstructionPeriod Context triple: [Iran–Turkey border, borderFenceConstructionPeriod, 2017–2020s]
-
A.
borderFenceConstructionStarted
chosen
Indicates that construction work has begun on a fence intended to serve as a border barrier between two areas or jurisdictions.
-
B.
borderNegotiationsPeriod
Indicates the time span during which negotiations or discussions about a border or boundary are taking place.
-
C.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
D.
hasBorderWallOrFence
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
-
E.
borderGuardDuty
Indicates that an entity is assigned to perform security or monitoring duties at a border or checkpoint.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: May 3, 2026, 4:03 p.m.