Triple
T35372981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran–Turkey border |
E1021824
|
entity |
| Predicate | adjacentProvince_Iran |
P62207
|
FINISHED |
| Object | West Azerbaijan Province |
—
|
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: West Azerbaijan Province | Statement: [Iran–Turkey border, adjacentProvince_Iran, West Azerbaijan Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentProvince_Iran Context triple: [Iran–Turkey border, adjacentProvince_Iran, West Azerbaijan Province]
-
A.
adjacentProvince
chosen
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
B.
adjacentProvince_Turkey
Indicates that one Turkish province is geographically adjacent to (shares a border with) another Turkish province.
-
C.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
D.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
-
E.
adjacentCanadianProvince
Indicates that two entities are Canadian provinces that share a common land or maritime border.
- 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_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:03 p.m.