Triple
T32200691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 238 Corridor Improvement Project controversy |
E822525
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | land use dispute |
C29174
|
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 dispute Context triple: [Route 238 Corridor Improvement Project controversy, instanceOf, land use dispute]
-
A.
land dispute
A land dispute is a conflict between parties over the ownership, boundaries, use, or rights associated with a specific piece of land or real property.
-
B.
resource rights dispute
A resource rights dispute is a conflict between parties over the ownership, access, control, or use of natural or economic resources such as land, water, minerals, or intellectual property.
-
C.
disputed territory
A disputed territory is a geographic area over which two or more parties claim sovereignty or control, without mutual agreement on its legal or political status.
-
D.
land claims settlement
A land claims settlement is a formal agreement that resolves disputes over land ownership or use rights, typically between governments and Indigenous or local communities, through compensation, land transfers, or legal recognition of rights.
-
E.
land use case
chosen
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.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:36 a.m.