Triple
T33117383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundesautobahn 5 |
E847493
|
entity |
| Predicate | isMajorTrafficCorridor |
P192581
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bundesautobahn 5, isMajorTrafficCorridor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTrafficCorridor Context triple: [Bundesautobahn 5, isMajorTrafficCorridor, true]
-
A.
isMajorTrafficRoute
Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
-
B.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
C.
isMajorRouteThrough
Indicates that a route serves as a primary or significant pathway passing through a specified area or location.
-
D.
isMajorTransportLink
Indicates that something serves as a primary or highly significant route or connection for transporting people or goods between places.
-
E.
isMajorTransportAxisIn
chosen
Indicates that a route or corridor functions as a primary or heavily used transportation pathway within a specified area or region.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 1, 2026, 1:27 a.m.