Triple
T4640931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Barrington, Illinois |
E101651
|
entity |
| Predicate | hasZoningOrdinances |
P49789
|
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: [Port Barrington, Illinois, hasZoningOrdinances, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZoningOrdinances Context triple: [Port Barrington, Illinois, hasZoningOrdinances, yes]
-
A.
hasLocalOrdinances
Indicates that a governing body or jurisdiction has established and enacted specific local ordinances or regulations.
-
B.
hasZoningPolicy
chosen
Indicates that a governing body or authority has established or adopted a specific zoning policy that regulates land use or development within its jurisdiction.
-
C.
foundOrdinances
Indicates that one entity has discovered, identified, or come across specific ordinances (such as laws, regulations, or decrees) associated with another entity or context.
-
D.
zoningCharacter
Indicates how the regulatory or functional nature of a geographic area is defined or classified in terms of land-use zoning.
-
E.
cityPlanningDesignation
Indicates how an area is officially classified or designated within urban or municipal planning (e.g., residential, commercial, industrial).
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a8fbd2c8190b593cd46ce8dfe0f |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:14 p.m.