Triple
T3115115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easton, Connecticut |
E65043
|
entity |
| Predicate | hasSignificantOpenSpace |
P5611
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Easton, Connecticut, hasSignificantOpenSpace, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantOpenSpace Context triple: [Easton, Connecticut, hasSignificantOpenSpace, yes]
-
A.
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.
-
B.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
C.
openSpaceType
chosen
Indicates the type or category of an open space associated with an entity (e.g., park, plaza, courtyard).
-
D.
hasGreenSpaces
Indicates that an entity includes or is associated with areas of vegetation or natural greenery, such as parks, gardens, or lawns.
-
E.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4e40bc48190b9b17c706a2450d5 |
completed | March 8, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.