Triple
T32503689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prager Platz |
E830727
|
entity |
| Predicate | hasSurroundingStreetNetwork |
P87577
|
FINISHED |
| Object | local streets of Wilmersdorf |
—
|
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: local streets of Wilmersdorf | Statement: [Prager Platz, hasSurroundingStreetNetwork, local streets of Wilmersdorf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingStreetNetwork Context triple: [Prager Platz, hasSurroundingStreetNetwork, local streets of Wilmersdorf]
-
A.
streetNetworkIncludes
Indicates that a given street network contains or encompasses a specified street segment, feature, or component as part of its structure.
-
B.
hasNearbyStreet
Indicates that one entity is located close to or adjacent to a street.
-
C.
hasNearbyStreetPattern
Indicates that one location has a street layout or configuration that is spatially close to, or in the vicinity of, another location’s street pattern.
-
D.
surroundedByStreet
chosen
Indicates that an entity is encircled or enclosed on all sides by one or more streets.
-
E.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 1, 2026, 12:59 a.m.