Triple
T11736421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindengracht |
E279037
|
entity |
| Predicate | hasStreetFunction |
P43747
|
FINISHED |
| Object | residential street |
—
|
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: residential street | Statement: [Lindengracht, hasStreetFunction, residential street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetFunction Context triple: [Lindengracht, hasStreetFunction, residential street]
-
A.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
B.
streetFunction
chosen
Indicates the functional role or primary use of a street within a transportation or urban context (e.g., residential, arterial, commercial access).
-
C.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
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.
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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4edced48190b7a59dd45921828e |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.