Triple
T25138752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarksburg Master Plan |
E629738
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-range planning document |
C17917
|
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: long-range planning document Context triple: [Clarksburg Master Plan, instanceOf, long-range planning document]
-
A.
long-term plan
A long-term plan is a structured, forward-looking strategy that outlines major goals and the sequence of actions needed to achieve them over an extended period of time.
-
B.
strategic document
A strategic document is a formal written plan that outlines an organization’s long-term goals, priorities, and actions for achieving its mission and competitive advantage.
-
C.
military planning document
A military planning document is a formal written plan that outlines objectives, strategies, resources, timelines, and contingencies for conducting military operations or activities.
-
D.
government strategy document
A government strategy document is an official, forward-looking plan that outlines a public authority’s long-term goals, priorities, and coordinated actions for addressing specific policy areas or national challenges.
-
E.
local and regional planning framework
chosen
A local and regional planning framework is a structured set of policies, processes, and tools that guide coordinated land use, infrastructure, and development decisions across municipalities and regions to achieve sustainable, equitable, and efficient growth.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:29 a.m.