Triple
T4720431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgewood |
E104750
|
entity |
| Predicate | zonedBy |
P49789
|
FINISHED |
| Object | City of Homewood zoning regulations |
—
|
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: City of Homewood zoning regulations | Statement: [Edgewood, zonedBy, City of Homewood zoning regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zonedBy Context triple: [Edgewood, zonedBy, City of Homewood zoning regulations]
-
A.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
B.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
C.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
D.
zoneConcept
Indicates that one entity is associated with, defined by, or operates within a particular zone or conceptual area specified by another entity.
-
E.
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.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.