Triple
T33349356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centreville, Michigan |
E853888
|
entity |
| Predicate | hasAreaLandUse |
P38195
|
FINISHED |
| Object | primarily 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: primarily residential | Statement: [Centreville, Michigan, hasAreaLandUse, primarily residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAreaLandUse Context triple: [Centreville, Michigan, hasAreaLandUse, primarily residential]
-
A.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
B.
hasLikelyLandUse
Indicates that an area or parcel is associated with a predicted or most probable type of land use (e.g., residential, commercial, agricultural).
-
C.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
D.
servesLandUseType
Indicates that one entity functions to support, accommodate, or provide services for a specified land use type.
-
E.
majorLandUse
chosen
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 1, 2026, 1:34 a.m.