Triple
T10883899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun City West |
E256992
|
entity |
| Predicate | hasZoningRestriction |
P96226
|
FINISHED |
| Object | age-restricted housing |
—
|
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: age-restricted housing | Statement: [Sun City West, hasZoningRestriction, age-restricted housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZoningRestriction Context triple: [Sun City West, hasZoningRestriction, age-restricted housing]
-
A.
hasZoningPolicy
Indicates that a governing body or authority has established or adopted a specific zoning policy that regulates land use or development within its jurisdiction.
-
B.
hasIndustrialZoning
Indicates that a given area or property is designated for industrial use under zoning regulations.
-
C.
zoningAuthority
Indicates that an entity has official power or jurisdiction to regulate land use and development within a specified area.
-
D.
hasZoningApproach
Indicates the type or method of zoning policy or strategy that is applied to or associated with an entity.
-
E.
hasRuralZoningCharacter
Indicates that a property or area possesses zoning attributes and regulations typical of rural land use.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751dc3518819090e03d81ea5c8aa9 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.