Triple
T5641577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Popish Plot |
E124278
|
entity |
| Predicate | mainAccusation |
P873
|
FINISHED |
| Object | Catholic plan to assassinate King Charles II |
—
|
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: Catholic plan to assassinate King Charles II | Statement: [Popish Plot, mainAccusation, Catholic plan to assassinate King Charles II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAccusation Context triple: [Popish Plot, mainAccusation, Catholic plan to assassinate King Charles II]
-
A.
accusationType
chosen
Indicates the specific category or nature of an accusation made by one party against another.
-
B.
accusationTarget
Indicates that one entity is the object or recipient of an accusation made by another entity.
-
C.
firstAccused
Indicates that the subject is the primary or earliest individual formally charged or blamed in a particular case or incident.
-
D.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
E.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c02286a14481908703ec1741343b76 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.