Triple
T13033079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col de la Schlucht |
E326489
|
entity |
| Predicate | roadOverPass |
P38947
|
FINISHED |
| Object | D417 |
—
|
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: D417 | Statement: [Col de la Schlucht, roadOverPass, D417]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadOverPass Context triple: [Col de la Schlucht, roadOverPass, D417]
-
A.
hasOverpass
chosen
Indicates that one location or route crosses over another via an elevated structure such as a bridge or overpass.
-
B.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
C.
streetNetwork
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
-
D.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
E.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efe72348190b52fb4068f5fb829 |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:54 p.m.