Triple
T24557034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howland Township |
E607543
|
entity |
| Predicate | isPrimarilyZonedAs |
P116763
|
FINISHED |
| Object | residential |
—
|
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: residential | Statement: [Howland Township, isPrimarilyZonedAs, residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimarilyZonedAs Context triple: [Howland Township, isPrimarilyZonedAs, residential]
-
A.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
B.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
C.
usesZoning
Indicates that one entity applies or relies on a zoning scheme, classification, or regulations established or provided by another entity.
-
D.
zonedUse
chosen
Indicates the designated or permitted type of land use assigned to a property or area under zoning regulations.
-
E.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
- 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f2af7c8190904f247ef29121d0 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.