Triple
T33614326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gift of Valor |
E861073
|
entity |
| Predicate | subjectMilitaryConflict |
P26327
|
FINISHED |
| Object | Iraq War |
—
|
NE NERFINISHED |
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: Iraq War | Statement: [The Gift of Valor, subjectMilitaryConflict, Iraq War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectMilitaryConflict Context triple: [The Gift of Valor, subjectMilitaryConflict, Iraq War]
-
A.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
B.
militaryConflictCovered
chosen
Indicates that one entity (such as a document, report, or media item) covers, describes, or reports on a specific military conflict involving another entity.
-
C.
militaryConflictIn
Indicates that a military conflict takes place within, or is geographically located in, a specified area or region.
-
D.
militaryConflictView
Indicates a perspective, interpretation, or representation of a specific military conflict or battle.
-
E.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 1:41 a.m.