Triple
T15501168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drottninggatan |
E378955
|
entity |
| Predicate | pedestrianizedSection |
P6741
|
FINISHED |
| Object | central Drottninggatan |
—
|
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: central Drottninggatan | Statement: [Drottninggatan, pedestrianizedSection, central Drottninggatan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pedestrianizedSection Context triple: [Drottninggatan, pedestrianizedSection, central Drottninggatan]
-
A.
pedestrianizedAreas
Indicates areas where vehicle traffic is restricted or removed so that pedestrians have priority use of the space.
-
B.
pedestrianizedSince
Indicates that an area or street has been designated for pedestrian use only starting from a specific point in time.
-
C.
pedestrianOnly
chosen
Indicates that a path, area, or route is designated exclusively for pedestrians and prohibits vehicle access.
-
D.
pedestrianizedDuring
Indicates that a location or route is designated for pedestrian-only use during a specified time period or interval.
-
E.
pedestrianRestrictions
Indicates that there are specific rules or limitations governing where or how pedestrians may travel or access an area.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fcb4e8c81908e4ab463e3ae252b |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:54 a.m.