Triple
T26235917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Gallantry Decorations |
E656165
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian military decoration system |
C36823
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Australian military decoration system Context triple: [Australian Gallantry Decorations, instanceOf, Australian military decoration system]
-
A.
Canadian military decoration
A Canadian military decoration is an official honour awarded by the Canadian government to recognize members of the armed forces or associated personnel for acts of bravery, distinguished service, or exceptional merit.
-
B.
military award system
A military award system is a structured framework for recognizing, categorizing, and administering honors, decorations, and medals granted to service members for acts of valor, merit, or distinguished service.
-
C.
set of military decorations
A set of military decorations is a collection of official honors, medals, and awards bestowed upon service members to recognize acts of valor, meritorious service, or distinguished achievement.
-
D.
orders, decorations, and medals system
chosen
A structured system for establishing, awarding, and managing honors such as orders, decorations, and medals to recognize and distinguish individuals or groups for their achievements, service, or merit.
-
E.
British military award
A British military award is an official decoration or medal conferred by the United Kingdom to recognize acts of bravery, distinguished service, or long and meritorious conduct by members of the armed forces.
- F. None of above.
Provenance (1 batch)
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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 9:01 p.m.