Triple
T36025048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treitlstraße |
E1042103
|
entity |
| Predicate | hasMotorVehicleTraffic |
P107210
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Treitlstraße, hasMotorVehicleTraffic, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotorVehicleTraffic Context triple: [Treitlstraße, hasMotorVehicleTraffic, yes]
-
A.
hasTrafficFeature
Indicates that an entity possesses or is associated with a specific traffic-related characteristic, element, or infrastructure feature.
-
B.
hasTruckTraffic
Indicates that there is truck-related vehicular movement or flow occurring on or through a specified location or route.
-
C.
hasTrafficMode
chosen
Indicates the mode or type of traffic associated with or applicable to an entity (e.g., pedestrian, vehicular, public transit).
-
D.
hasMotorVehicleAccess
Indicates that an entity is permitted to use or operate a motor vehicle within a specified area, context, or under certain conditions.
-
E.
hasTrafficControl
Indicates that some form of traffic management or regulation mechanism is present or applied to a given route, intersection, or transportation element.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 3, 2026, 4:07 p.m.