Triple
T32200692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 238 Corridor Improvement Project controversy |
E822525
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | infrastructure project controversy |
C18730
|
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: infrastructure project controversy Context triple: [Route 238 Corridor Improvement Project controversy, instanceOf, infrastructure project controversy]
-
A.
infrastructure project
An infrastructure project is a large-scale, organized effort to plan, design, and construct foundational physical systems—such as transportation, utilities, and public facilities—that support a community’s or region’s economic and social activities.
-
B.
public policy controversy
A public policy controversy is a sustained, often polarized dispute among stakeholders over the goals, design, implementation, or consequences of government actions or regulations.
-
C.
controversy
chosen
Controversy is a state of public disagreement or heated debate arising from conflicting opinions, values, or interpretations about a particular issue, event, or decision.
-
D.
contentious case
A contentious case is a legal dispute between opposing parties brought before a court or tribunal for adjudication on contested rights or obligations.
-
E.
proposed dam project
A proposed dam project is a planned infrastructure initiative to construct a barrier across a waterway for purposes such as water storage, flood control, energy generation, or irrigation, pending approval and implementation.
- 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.