Triple
T16863159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberalp Pass |
E409970
|
entity |
| Predicate | roadManagedBy |
P5944
|
FINISHED |
| Object | Swiss authorities |
—
|
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: Swiss authorities | Statement: [Oberalp Pass, roadManagedBy, Swiss authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadManagedBy Context triple: [Oberalp Pass, roadManagedBy, Swiss authorities]
-
A.
roadNetworkJurisdiction
Indicates the authority or entity responsible for managing, regulating, or maintaining a given segment of the road network.
-
B.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
C.
roadSystemRole
Indicates the specific functional role or responsibility an entity has within a road or transportation network system.
-
D.
roadOperator
chosen
Indicates that one entity is responsible for operating, managing, or maintaining a particular road or road network.
-
E.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b50488fc8190b3b646543c3ba476 |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.