Triple
T15648868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coltishall |
E376251
|
entity |
| Predicate | hasPublicOpenSpace |
P37084
|
FINISHED |
| Object | riverside common |
—
|
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: riverside common | Statement: [Coltishall, hasPublicOpenSpace, riverside common]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicOpenSpace Context triple: [Coltishall, hasPublicOpenSpace, riverside common]
-
A.
hasPublicSpaces
chosen
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
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.
hasOutdoorSpaceType
Indicates the specific kind of outdoor area associated with an entity, such as a balcony, terrace, garden, or patio.
-
D.
isUrbanOpenSpace
Indicates that a given area functions as an open, publicly accessible space within an urban environment.
-
E.
hasGreenSpaces
Indicates that an entity includes or is associated with areas of vegetation or natural greenery, such as parks, gardens, or lawns.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed7212c8190be6ff76afa25f7ca |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.