Triple
T9433512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coyote Springs, Nevada |
E227442
|
entity |
| Predicate | plannedLandUse |
P12134
|
FINISHED |
| Object | 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: residential | Statement: [Coyote Springs, Nevada, plannedLandUse, residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedLandUse Context triple: [Coyote Springs, Nevada, plannedLandUse, residential]
-
A.
plannedUseOf
chosen
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
B.
landUseContext
Indicates the contextual setting or circumstances under which a particular piece of land is used or designated for a specific purpose.
-
C.
otherLandUse
Indicates that the land is used for purposes that do not fall into any of the primary or predefined land-use categories.
-
D.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
E.
primaryLandUse
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e61a114819081fc4a2ad39c96ba |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.