Triple
T21910719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Service Ribbon |
E541049
|
entity |
| Predicate | isNonCombatAward |
P78221
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Army Service Ribbon, isNonCombatAward, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonCombatAward Context triple: [Army Service Ribbon, isNonCombatAward, true]
-
A.
isCivilianAward
Indicates that an award is designated for civilians rather than military or combat-related recipients.
-
B.
isMilitaryAwardFor
Indicates that something is a military honor or decoration given in recognition of a specific action, service, or achievement.
-
C.
isNonCampaignMedal
chosen
Indicates that a medal is classified as a non-campaign medal, meaning it is not awarded for participation in a specific military campaign or operation.
-
D.
isGallantryAward
Indicates that the subject is a formal gallantry award, i.e., an honor conferred in recognition of exceptional bravery or valor.
-
E.
militaryAward
Indicates that an entity has received or been granted a specific military honor, decoration, or award.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121d9796881909fc1454a7b61b8fe |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:40 p.m.