Triple
T37508138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Table |
E932148
|
entity |
| Predicate | missionResolution |
P21239
|
FINISHED |
| Object | Automated combat simulation |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Automated combat simulation | Statement: [Command Table, missionResolution, Automated combat simulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionResolution Context triple: [Command Table, missionResolution, Automated combat simulation]
-
A.
missionOutcome
chosen
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
-
B.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
C.
resolution
Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
-
D.
resolutionIdea
Indicates a proposed method, plan, or approach intended to resolve or address a particular issue, conflict, or problem.
-
E.
missionEnd
Indicates that a mission has concluded or reached its final state or outcome.
- F. None of above.
Provenance (3 batches)
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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.