Triple
T8246521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | demon core |
E192861
|
entity |
| Predicate | associatedWithRisk |
P62537
|
FINISHED |
| Object | prompt criticality |
—
|
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: prompt criticality | Statement: [demon core, associatedWithRisk, prompt criticality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRisk Context triple: [demon core, associatedWithRisk, prompt criticality]
-
A.
associatedWithUse
Indicates a relationship where one entity is connected to or involved in the use or utilization of another entity.
-
B.
riskElement
chosen
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
-
C.
riskAddressed
Indicates that a particular risk has been identified and is being mitigated, managed, or otherwise handled by an associated action, control, or measure.
-
D.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
E.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb787414508190a08cf47d1545ce50 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.