Triple
T2092537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Valorous Unit Award |
E32701
|
entity |
| Predicate | natureOfHeroism |
P27803
|
FINISHED |
| Object | gallantry in action against an armed enemy |
—
|
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: gallantry in action against an armed enemy | Statement: [Army Valorous Unit Award, natureOfHeroism, gallantry in action against an armed enemy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfHeroism Context triple: [Army Valorous Unit Award, natureOfHeroism, gallantry in action against an armed enemy]
-
A.
typeOfBravery
chosen
Indicates a specific kind or category of bravery that characterizes an entity’s courageous behavior or action.
-
B.
nonCombatHeroismScope
Indicates the extent or context in which acts of heroism occur outside of direct combat or fighting situations.
-
C.
primacyOfHonorOver
Indicates that one entity is regarded as having higher honor, status, or precedence than another.
-
D.
reasonForKnighthood
Indicates the specific cause, achievement, or merit for which an individual was granted knighthood.
-
E.
moralTheme
Indicates that a work, event, or situation embodies or conveys a particular ethical lesson, value, or moral principle.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba774ca881909f83cf65ffeb24bb |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.