Triple
T8701531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pohjoisesplanadi |
E206542
|
entity |
| Predicate | hasPublicSpaceRelation |
P31591
|
FINISHED |
| Object | borders major urban park (Esplanadi) |
—
|
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: borders major urban park (Esplanadi) | Statement: [Pohjoisesplanadi, hasPublicSpaceRelation, borders major urban park (Esplanadi)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicSpaceRelation Context triple: [Pohjoisesplanadi, hasPublicSpaceRelation, borders major urban park (Esplanadi)]
-
A.
hasPublicSpaceAlong
chosen
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
B.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
C.
isInPublicSpace
Indicates that an entity is located within a space that is publicly accessible or open to the general public.
-
D.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
-
E.
hasCommonSpace
Indicates that two or more entities share access to the same physical or virtual area intended for joint or overlapping use.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58b38cf88190bfdcbac9c340cb96 |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.