Triple
T27978452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross of Merit for Bravery |
E706551
|
entity |
| Predicate | riskLevelRequired |
P66053
|
FINISHED |
| Object | direct danger to life or health |
—
|
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: direct danger to life or health | Statement: [Cross of Merit for Bravery, riskLevelRequired, direct danger to life or health]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskLevelRequired Context triple: [Cross of Merit for Bravery, riskLevelRequired, direct danger to life or health]
-
A.
riskLevel
Indicates the degree of potential harm, loss, or adverse outcome associated with a particular situation, action, or entity.
-
B.
riskRequirement
chosen
Indicates that one entity specifies or imposes a required level or type of risk consideration that another entity must meet or address.
-
C.
riskListedBy
Indicates that a risk has been documented, identified, or cataloged by a particular agent or source.
-
D.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
E.
riskSensitivity
Indicates how strongly an entity’s decisions or behavior change in response to potential risk or uncertainty.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b66e9248190974ea3d66f984de1 |
completed | May 2, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:42 p.m.