Triple
T26880723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethany, Connecticut |
E676884
|
entity |
| Predicate | hasOpenSpacePreservationPolicy |
P170960
|
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: [Bethany, Connecticut, hasOpenSpacePreservationPolicy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpenSpacePreservationPolicy Context triple: [Bethany, Connecticut, hasOpenSpacePreservationPolicy, yes]
-
A.
hasGreenbeltPolicy
Indicates that an entity has adopted or enforces a policy to protect designated greenbelt areas from development or certain land uses.
-
B.
hasOpenSpacePreserve
Indicates that one entity possesses, contains, or is associated with an area designated as an open space preserve.
-
C.
hasOpenSpaceEasements
Indicates that one entity holds legal open space easement rights or restrictions over another entity or its land.
-
D.
hasPublicSpacePolicy
Indicates that an entity has an established policy governing the use, management, or regulation of public spaces.
-
E.
hasConservationLand
Indicates that an entity possesses, manages, or is associated with land designated for environmental or natural resource conservation.
- F. None of above. chosen
Provenance (4 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 27, 2026, 5:39 a.m.