Triple
T18126703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorbergstraße |
E433893
|
entity |
| Predicate | isAccessStreetFor |
P25669
|
FINISHED |
| Object | local residential buildings |
—
|
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 residential buildings | Statement: [Vorbergstraße, isAccessStreetFor, local residential buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessStreetFor Context triple: [Vorbergstraße, isAccessStreetFor, local residential buildings]
-
A.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
B.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
-
C.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
-
D.
hasPedestrianAccessTo
chosen
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
E.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddee1efc8190b04324b98de5c9d0 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.