Triple
T28692786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decimus Junius Brutus Albinus |
E729330
|
entity |
| Predicate | victimOfConspiracy |
P130740
|
FINISHED |
| Object | Julius Caesar |
—
|
NE NERFINISHED |
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: Julius Caesar | Statement: [Decimus Junius Brutus Albinus, victimOfConspiracy, Julius Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimOfConspiracy Context triple: [Decimus Junius Brutus Albinus, victimOfConspiracy, Julius Caesar]
-
A.
conspiracy
Indicates a secret agreement or collaboration between multiple entities to plan or carry out an unlawful, deceptive, or harmful act.
-
B.
conspirator
Indicates that an entity participates with others in planning or carrying out a secret or illicit scheme or action.
-
C.
positionOnConspiracy
Indicates the stance or viewpoint an entity holds regarding a particular conspiracy or conspiracy theory.
-
D.
victimOfAccusation
Indicates that an entity is the target or subject of an accusation made by another party.
-
E.
victimOfMurderPlot
chosen
Indicates that one entity is the intended target or victim in another entity’s plan or plot to commit murder.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 5:37 a.m.