Triple
T33364035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | München-Nord interchange |
E854301
|
entity |
| Predicate | roadNetworkLevel |
P155879
|
FINISHED |
| Object | national |
—
|
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: national | Statement: [München-Nord interchange, roadNetworkLevel, national]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNetworkLevel Context triple: [München-Nord interchange, roadNetworkLevel, national]
-
A.
roadSystemLevel
chosen
Indicates the classification or hierarchy level of a road within a broader transportation or road network system.
-
B.
roadNetworkContext
Indicates the contextual relationship between elements within a road network, such as how roads, intersections, and related infrastructure are organized or interact.
-
C.
roadNetworkDensity
Indicates the concentration of roads within a given area, reflecting how densely the transportation network is developed.
-
D.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
E.
roadNetworkJurisdiction
Indicates the authority or entity responsible for managing, regulating, or maintaining a given segment of the road 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.