Triple
T20198323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Combat Mission Teams |
E493145
|
entity |
| Predicate | supportsWarfightingFunction |
P105707
|
FINISHED |
| Object | mission command |
—
|
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: mission command | Statement: [Army Combat Mission Teams, supportsWarfightingFunction, mission command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsWarfightingFunction Context triple: [Army Combat Mission Teams, supportsWarfightingFunction, mission command]
-
A.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
-
B.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
-
C.
functionInWarfare
chosen
Indicates the role, purpose, or operational function that something serves within a military or warfare context.
-
D.
isCombatSupportUnit
Indicates that the unit’s primary role is to provide operational or logistical support to combat forces rather than engage directly in frontline fighting.
-
E.
supportsMissionArea
Indicates that one entity contributes to, enables, or aligns with the objectives and activities of a specified mission area.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66d8afe408190a7a9202ed67698e6 |
completed | April 20, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.