Triple
T36251578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana University Bloomington campus master plan |
E891816
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-term planning document |
C7550
|
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-term planning document Context triple: [Indiana University Bloomington campus master plan, instanceOf, long-term planning document]
-
A.
long-term plan
chosen
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.
architectural planning document
An architectural planning document is a formal artifact that captures and communicates the intended structure, components, constraints, and design decisions of a system or building before implementation or construction begins.
-
E.
medium-term development plan
A medium-term development plan is a structured roadmap outlining specific goals, strategies, and actions to be achieved over an intermediate time horizon, typically three to five years, to guide sustainable growth and improvement.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.