Triple
T17353131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force lightning |
E421862
|
entity |
| Predicate | riskToUser |
P127159
|
FINISHED |
| Object | self‑injury if reflected |
—
|
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: self‑injury if reflected | Statement: [Force lightning, riskToUser, self‑injury if reflected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskToUser Context triple: [Force lightning, riskToUser, self‑injury if reflected]
-
A.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
-
B.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
C.
riskToSpeaker
Indicates that the action, event, or situation poses a potential danger, harm, or adverse consequence to the speaker.
-
D.
riskElement
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
-
E.
riskLevel
Indicates the degree of potential harm, loss, or adverse outcome associated with a particular situation, action, or entity.
- F. None of above. chosen
Provenance (4 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2e660c81908700aed5c42e9043 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.