Triple
T5682233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Lifesaving Medal |
E125224
|
entity |
| Predicate | nonCombatantDecoration |
P55953
|
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: [Silver Lifesaving Medal, nonCombatantDecoration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonCombatantDecoration Context triple: [Silver Lifesaving Medal, nonCombatantDecoration, true]
-
A.
isNonCombatDecoration
chosen
Indicates that an award or decoration is given for non-combat service or achievements rather than for participation in direct combat.
-
B.
isNonMilitaryDecoration
Indicates that an honor or award is a decoration that is not associated with military service or military institutions.
-
C.
isCombatDecoration
Indicates that an award or decoration is specifically given for participation or valor in combat or military conflict.
-
D.
isCombatOnlyDecoration
Indicates that the object serves purely decorative purposes and is only visible or relevant during combat, without affecting gameplay outside combat.
-
E.
combatOrNonCombat
Indicates whether an entity is involved in combat activities or is in a non-combat role or situation.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.