Triple
T20223304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bassianus |
E495312
|
entity |
| Predicate | framedForCrime |
P114296
|
FINISHED |
| Object | treason against Saturninus |
—
|
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: treason against Saturninus | Statement: [Bassianus, framedForCrime, treason against Saturninus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: framedForCrime Context triple: [Bassianus, framedForCrime, treason against Saturninus]
-
A.
frameForCrime
chosen
Indicates causing someone to be falsely perceived or officially treated as responsible for a crime they did not commit.
-
B.
arrestedFor
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
C.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
D.
pursuedForCrime
Indicates that an entity is being actively sought or chased by authorities or others because of an alleged or committed crime.
-
E.
crimeCharged
Indicates that legal authorities have formally accused an entity of committing a specific crime.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd827708190b798a30f4e7d533f |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.