Triple
T2369935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Cross Medal |
E46062
|
entity |
| Predicate | typeOfGallantry |
P27803
|
FINISHED |
| Object | combat gallantry |
—
|
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: combat gallantry | Statement: [Gold Cross Medal, typeOfGallantry, combat gallantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfGallantry Context triple: [Gold Cross Medal, typeOfGallantry, combat gallantry]
-
A.
militaryAward
Indicates that an entity has received or been granted a specific military honor, decoration, or award.
-
B.
typeOfBravery
chosen
Indicates a specific kind or category of bravery that characterizes an entity’s courageous behavior or action.
-
C.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
-
D.
wartimeAward
Indicates that an entity received an award or honor specifically in the context of wartime or military conflict.
-
E.
battleHonors
Indicates that an entity has been awarded or is associated with specific honors or distinctions earned through participation in battles or military engagements.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc76f5aec8190867d621e6849258c |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.