Triple
T35372964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran–Turkey border |
E1021824
|
entity |
| Predicate | majorRoadCorridor |
P73526
|
FINISHED |
| Object | D100 highway (Turkey) |
—
|
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: D100 highway (Turkey) | Statement: [Iran–Turkey border, majorRoadCorridor, D100 highway (Turkey)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRoadCorridor Context triple: [Iran–Turkey border, majorRoadCorridor, D100 highway (Turkey)]
-
A.
majorTransportCorridor
Indicates that a route or pathway functions as a primary, high-capacity channel for transporting people or goods between significant locations.
-
B.
mainRoadInfrastructure
Indicates that a road segment functions as a primary or major route within the transportation infrastructure network.
-
C.
roadCorridorIncludes
chosen
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
-
D.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
E.
isMajorTrafficRoute
Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
- 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_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 3, 2026, 4:03 p.m.