Triple
T23354820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundy standoff |
E593014
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | land-use conflict |
C10493
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: land-use conflict Context triple: [Bundy standoff, instanceOf, land-use conflict]
-
A.
land use case
A land use case is a specific scenario or application that illustrates how a particular area of land is designated, managed, and regulated for activities such as residential, commercial, agricultural, industrial, or recreational purposes.
-
B.
land-use control
Land-use control is the set of legal and administrative mechanisms by which governments and authorities regulate how land may be developed, used, and conserved within a given jurisdiction.
-
C.
resource conflict
chosen
A resource conflict occurs when multiple entities or processes compete for the same limited resources, leading to contention, delays, or suboptimal outcomes.
-
D.
land use plan
A land use plan is a strategic document that guides the allocation, development, and conservation of land within a defined area to balance environmental, social, and economic objectives.
-
E.
contested territory
A contested territory is a geographic area over which two or more parties assert overlapping or conflicting claims of ownership, control, or sovereignty.
- F. None of above.
Provenance (1 batch)
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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:20 p.m.