Triple
T21425423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trg Nikole Šubića Zrinskog 19 |
E528540
|
entity |
| Predicate | publicSpaceTypeNearby |
P75188
|
FINISHED |
| Object | city park 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: city park square | Statement: [Trg Nikole Šubića Zrinskog 19, publicSpaceTypeNearby, city park square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicSpaceTypeNearby Context triple: [Trg Nikole Šubića Zrinskog 19, publicSpaceTypeNearby, city park square]
-
A.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
B.
nearPublicSpace
Indicates that one entity is located close to or in the immediate vicinity of a public space.
-
C.
nearbyEnvironment
Indicates that an entity is located in or affected by the immediate surrounding conditions or context of another entity.
-
D.
nearbyFacilityType
chosen
Indicates that a facility of a specified type is located close to a given reference entity or location.
-
E.
hasOpenSpaceNearby
Indicates that an entity is located near or adjacent to an area that is open, unobstructed, or undeveloped.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b3e2dc408190a4c66a433258f920 |
completed | April 22, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.