Triple
T2566185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Corps |
E57355
|
entity |
| Predicate | operationalEmphasis |
P17512
|
FINISHED |
| Object | multi-domain operations |
—
|
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: multi-domain operations | Statement: [I Corps, operationalEmphasis, multi-domain operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalEmphasis Context triple: [I Corps, operationalEmphasis, multi-domain operations]
-
A.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
B.
strategyEmphasis
chosen
Indicates an entity’s primary focus or priority within a broader strategy or plan.
-
C.
operationalRequirement
Indicates that one entity specifies a condition or capability that must be met for another entity to function or operate as intended.
-
D.
operationalCommand
Indicates that one entity issues or holds authoritative control over the actions or operations of another entity.
-
E.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35ef22c8190966612cc75f69eca |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.