Triple
T8054858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White City, Utah |
E187772
|
entity |
| Predicate | residentialUse |
P25942
|
FINISHED |
| Object | primarily single-family 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: primarily single-family housing | Statement: [White City, Utah, residentialUse, primarily single-family housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residentialUse Context triple: [White City, Utah, residentialUse, primarily single-family housing]
-
A.
houseUse
Indicates how a house or dwelling is used or purposed (e.g., residential, commercial, mixed-use).
-
B.
isResidential
chosen
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
C.
residentialSystem
Indicates a system, structure, or arrangement that is specifically designed for, associated with, or functioning within residential living environments.
-
D.
residenceUsedFor
Indicates that a particular residence is used for a specific purpose, function, or activity.
-
E.
nonResidential
Indicates that something is not intended or used for residential or living purposes.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fa16804819094926ff2ff053c80 |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.