Triple
T21775779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danmarks gate |
E537569
|
entity |
| Predicate | hasStreetHierarchyRole |
P145907
|
FINISHED |
| Object | minor road |
—
|
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: minor road | Statement: [Danmarks gate, hasStreetHierarchyRole, minor road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetHierarchyRole Context triple: [Danmarks gate, hasStreetHierarchyRole, minor road]
-
A.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
B.
hasSideStreetRole
Indicates that an entity holds a specific functional or contextual role in relation to a side street.
-
C.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
D.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
-
E.
hasStreetGridFeature
Indicates that a location or area possesses a specific characteristic or element of a street grid layout, such as a particular pattern, structure, or feature of its road network.
- F. None of above. chosen
Provenance (4 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f046291d808190b5111a8d4819909f |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:51 p.m.