Triple
T3432279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village of Harriman, New York |
E72365
|
entity |
| Predicate | hasZoningRegulations |
P16838
|
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: [Village of Harriman, New York, hasZoningRegulations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZoningRegulations Context triple: [Village of Harriman, New York, hasZoningRegulations, yes]
-
A.
zoningCharacter
Indicates how the regulatory or functional nature of a geographic area is defined or classified in terms of land-use zoning.
-
B.
hasLocalOrdinances
chosen
Indicates that a governing body or jurisdiction has established and enacted specific local ordinances or regulations.
-
C.
isPlannedCommunity
Indicates that a community has been intentionally designed and developed according to a coordinated plan rather than growing organically.
-
D.
hasPedestrianZoneStatus
Indicates whether an area or segment is designated as a pedestrian-only or pedestrian-priority zone and its corresponding status.
-
E.
regulatesArea
Indicates that one entity exercises control or governance over the spatial extent, scope, or domain of another entity.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9c077d48190bee40795cab3e422 |
completed | March 8, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.