Triple
T30919356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Requiem |
E787673
|
entity |
| Predicate | riskToAuthor |
P99883
|
FINISHED |
| Object | could not be written down safely |
—
|
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: could not be written down safely | Statement: [Requiem, riskToAuthor, could not be written down safely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskToAuthor Context triple: [Requiem, riskToAuthor, could not be written down safely]
-
A.
riskToUser
Indicates that something poses a potential danger, harm, or adverse impact to the user.
-
B.
riskToSpeaker
chosen
Indicates that the action, event, or situation poses a potential danger, harm, or adverse consequence to the speaker.
-
C.
riskToPublic
Indicates that something poses a potential danger, harm, or adverse impact to the general public or community.
-
D.
riskListedBy
Indicates that a risk has been documented, identified, or cataloged by a particular agent or source.
-
E.
riskToMembers
Indicates that something poses a potential danger, harm, or adverse impact to the members of a group or organization.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692b478388190a28a8ee41ac02b2a |
completed | May 3, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:51 p.m.