Triple
T5182256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Superior Unit Award |
E116947
|
entity |
| Predicate | combatRelated |
P61941
|
FINISHED |
| Object | no (primarily non‑combat recognition) |
—
|
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: no (primarily non‑combat recognition) | Statement: [Army Superior Unit Award, combatRelated, no (primarily non‑combat recognition)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatRelated Context triple: [Army Superior Unit Award, combatRelated, no (primarily non‑combat recognition)]
-
A.
wasWoundedIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or conflict.
-
B.
armedConflictTheatre
Indicates a geographic area or location where an armed conflict takes place or is actively occurring.
-
C.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
D.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
E.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
- F. None of above. chosen
Provenance (4 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd799d50388190bf2b7dfdd90949e9 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:46 p.m.