Triple
T2502667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brückenstraße (Chemnitz) |
E52499
|
entity |
| Predicate | hasRoadFunction |
P20752
|
FINISHED |
| Object | inner-city connector |
—
|
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: inner-city connector | Statement: [Brückenstraße (Chemnitz), hasRoadFunction, inner-city connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadFunction Context triple: [Brückenstraße (Chemnitz), hasRoadFunction, inner-city connector]
-
A.
hasRoadConfiguration
Indicates that there exists a specific arrangement or layout of roads associated with or characterizing an entity.
-
B.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
C.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
D.
onRoad
Indicates that one entity is located on, traveling along, or otherwise situated upon a road.
-
E.
hasTrafficFunction
chosen
Indicates that an entity performs, supports, or is assigned a specific function or role related to traffic management or control.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1cb4f6481908d4e0a1dc0d84d3c |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.