Triple
T28662721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casca |
E725508
|
entity |
| Predicate | conspiratorAlongside |
P21638
|
FINISHED |
| Object | Marcus Junius Brutus |
—
|
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: Marcus Junius Brutus | Statement: [Casca, conspiratorAlongside, Marcus Junius Brutus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conspiratorAlongside Context triple: [Casca, conspiratorAlongside, Marcus Junius Brutus]
-
A.
conspirator
Indicates that an entity participates with others in planning or carrying out a secret or illicit scheme or action.
-
B.
metConspiratorsAt
Indicates that an individual met with one or more co-conspirators at a specific place and/or time as part of a conspiracy.
-
C.
allegesCollaborationWith
Indicates that one party claims or asserts that another party has worked together or cooperated with a specified entity.
-
D.
convictedAlongside
Indicates that one entity was convicted in a legal proceeding together with another entity as co-defendants in the same case or trial.
-
E.
partnerInCrime
chosen
Indicates a relationship where two or more entities collaborate closely in committing or planning wrongful, illicit, or mischievous acts together.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:59 a.m.