Triple
T21101520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INCOSE Systems Engineering Vision |
E519916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic document |
C44254
|
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: strategic document Context triple: [INCOSE Systems Engineering Vision, instanceOf, strategic document]
-
A.
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.
-
B.
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.
-
C.
strategic assessment
A strategic assessment is a systematic evaluation of an organization’s internal capabilities and external environment to inform long-term decisions and competitive positioning.
-
D.
founding document
A founding document is an authoritative text that formally establishes an organization, institution, or state by defining its core principles, structure, and governing rules.
-
E.
regulatory document
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
- F. None of above. chosen
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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:53 p.m.