Triple
T23288572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbeidergata |
E589961
|
entity |
| Predicate | hasPublicSpaceTypeNearby |
P126415
|
FINISHED |
| Object | public square |
—
|
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: public square | Statement: [Arbeidergata, hasPublicSpaceTypeNearby, public square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicSpaceTypeNearby Context triple: [Arbeidergata, hasPublicSpaceTypeNearby, public square]
-
A.
hasOpenSpaceNearby
Indicates that an entity is located near or adjacent to an area that is open, unobstructed, or undeveloped.
-
B.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
C.
nearPublicSpace
chosen
Indicates that one entity is located close to or in the immediate vicinity of a public space.
-
D.
hasNearbyPropertyType
Indicates that one entity has another entity of a specified property type located in close physical proximity to it.
-
E.
hasNearbyInfrastructureType
Indicates that an entity is located close to infrastructure of a specified type.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19649570c8190b565fafa55b1f886 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:01 p.m.