Triple
T19154863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Apostolic Preferences of the Society of Jesus (2019–2029) |
E468905
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mission priorities |
C37817
|
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: mission priorities Context triple: [Universal Apostolic Preferences of the Society of Jesus (2019–2029), instanceOf, mission priorities]
-
A.
mission priorities framework
chosen
A mission priorities framework is a structured model that organizes and ranks an organization’s goals and initiatives to ensure resources and actions align with its core mission and strategic objectives.
-
B.
mission manifesto
A mission manifesto is a clear, compelling declaration that articulates an organization’s core purpose, values, and long-term intentions, guiding decisions and inspiring aligned action.
-
C.
military mission
A military mission is a coordinated operation undertaken by armed forces to achieve specific strategic, operational, or tactical objectives within defined constraints and rules of engagement.
-
D.
military objective
A military objective is any object, location, or force which by its nature, location, purpose, or use makes an effective contribution to military action and whose total or partial destruction, capture, or neutralization offers a definite military advantage.
-
E.
mission system
A mission system is a coordinated set of processes, tools, and resources designed to plan, execute, monitor, and evaluate the completion of specific operational or strategic objectives.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:06 p.m.