Triple
T13141872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayou Vista, Texas |
E312227
|
entity |
| Predicate | zoningDominantType |
P727
|
FINISHED |
| Object | single-family 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: single-family residential | Statement: [Bayou Vista, Texas, zoningDominantType, single-family residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoningDominantType Context triple: [Bayou Vista, Texas, zoningDominantType, single-family residential]
-
A.
zoningCharacter
chosen
Indicates how the regulatory or functional nature of a geographic area is defined or classified in terms of land-use zoning.
-
B.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
-
C.
dominatingFeature
Indicates that one feature stands out as the most prominent or influential characteristic in relation to others.
-
D.
hasZoningRestriction
Indicates that an entity is subject to a specific zoning-related limitation or regulatory constraint.
-
E.
zoningAuthority
Indicates that an entity has official power or jurisdiction to regulate land use and development within a specified area.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b84f1081908b9e2d54a64d4c2d |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:10 p.m.