Triple
T38363560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prophecy |
E892361
|
entity |
| Predicate | causeOfMutationInPlot |
P694
|
FINISHED |
| Object | mercury pollution |
—
|
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: mercury pollution | Statement: [Prophecy, causeOfMutationInPlot, mercury pollution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfMutationInPlot Context triple: [Prophecy, causeOfMutationInPlot, mercury pollution]
-
A.
causeInStory
Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
-
B.
disfigurementCauseInStory
Indicates that one entity is the cause or source of another entity’s disfigurement within the context of a narrative or story.
-
C.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
influencesPlotOf
Indicates that one entity has an effect on or helps shape the storyline or narrative development of another entity.
-
E.
problemInPlot
Indicates that there is an issue, flaw, or inconsistency present within the structure or progression of a plot.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 3, 2026, 4:31 p.m.