Triple
T35542135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rennweg |
E1027088
|
entity |
| Predicate | isPedestrianStreet |
P46481
|
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: [Rennweg, isPedestrianStreet, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPedestrianStreet Context triple: [Rennweg, isPedestrianStreet, true]
-
A.
isPedestrianGateway
Indicates that something serves as an access point or entrance specifically intended for use by pedestrians.
-
B.
hasPedestrianZoneStatus
chosen
Indicates whether an area or segment is designated as a pedestrian-only or pedestrian-priority zone and its corresponding status.
-
C.
isPedestrianFocus
Indicates that the primary attention or design consideration is directed toward pedestrians in a given context or environment.
-
D.
pedestrianRestrictions
Indicates that there are specific rules or limitations governing where or how pedestrians may travel or access an area.
-
E.
isUrbanStreet
Indicates that a given street is located within an urban area or city environment rather than a rural or suburban setting.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.