Triple
T14792989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Berwick witch trials |
E347702
|
entity |
| Predicate | allegedPlot |
P47190
|
FINISHED |
| Object | to kill King James VI |
—
|
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: to kill King James VI | Statement: [North Berwick witch trials, allegedPlot, to kill King James VI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedPlot Context triple: [North Berwick witch trials, allegedPlot, to kill King James VI]
-
A.
allegedPlots
chosen
Indicates that one entity is accused or suspected of planning or conspiring to carry out harmful or illicit actions involving another entity.
-
B.
hasPoliticalPlot
Indicates that the subject work contains a storyline or narrative element centered on politics, political events, or political power struggles.
-
C.
allegedImpostor
Indicates that one entity is claimed or suspected to be fraudulently posing as another entity.
-
D.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
E.
partOfPlot
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5ec43c8190ad7a10a556519bb0 |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.