Triple
T14670187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Calpurnius Piso |
E344488
|
entity |
| Predicate | aimOfConspiracy |
P64674
|
FINISHED |
| Object | overthrow Nero |
—
|
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: overthrow Nero | Statement: [Gaius Calpurnius Piso, aimOfConspiracy, overthrow Nero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfConspiracy Context triple: [Gaius Calpurnius Piso, aimOfConspiracy, overthrow Nero]
-
A.
conspiracy
Indicates a secret agreement or collaboration between multiple entities to plan or carry out an unlawful, deceptive, or harmful act.
-
B.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
C.
conspirator
Indicates that an entity participates with others in planning or carrying out a secret or illicit scheme or action.
-
D.
aimOfOtherSide
Indicates that one party’s goal or intended outcome is directed toward or defined in relation to the opposing or counterpart side in a relationship or interaction.
-
E.
aimOfCondemnation
Indicates that an act of condemnation is directed toward a particular target or objective.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54ef2908190b189ced65eec434a |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.