Triple
T4915416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight 4th Class |
E110334
|
entity |
| Predicate | typeOfBraveryRecognized |
P52884
|
FINISHED |
| Object | bravery in the face of the 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: bravery in the face of the enemy | Statement: [Knight 4th Class, typeOfBraveryRecognized, bravery in the face of the enemy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBraveryRecognized Context triple: [Knight 4th Class, typeOfBraveryRecognized, bravery in the face of the enemy]
-
A.
typeOfBravery
Indicates a specific kind or category of bravery that characterizes an entity’s courageous behavior or action.
-
B.
militaryAwardType
chosen
Indicates the specific category or kind of military honor or decoration associated with an award.
-
C.
fieldOfRecognition
Indicates the domain, discipline, or area in which an entity is formally acknowledged, honored, or recognized.
-
D.
militaryAward
Indicates that an entity has received or been granted a specific military honor, decoration, or award.
-
E.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa404f881908b4f983983ac7076 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.