Triple
T30465256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Publius Cornelius Dolabella |
E775118
|
entity |
| Predicate | tookOwnLifeToAvoid |
P118269
|
FINISHED |
| Object | capture by forces of the Liberators |
—
|
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: capture by forces of the Liberators | Statement: [Publius Cornelius Dolabella, tookOwnLifeToAvoid, capture by forces of the Liberators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookOwnLifeToAvoid Context triple: [Publius Cornelius Dolabella, tookOwnLifeToAvoid, capture by forces of the Liberators]
-
A.
killedHimselfAfter
chosen
Indicates that an individual committed suicide following a specified event or time.
-
B.
threatenedToKill
Indicates that one entity has made a threat or expressed an intention to kill another entity.
-
C.
killsSelfFor
Indicates that an entity intentionally causes its own death for the sake or benefit of another specified entity.
-
D.
ultimatelyRefusesToKill
Indicates that an entity, despite prior opportunity or intent, finally decides not to kill another entity.
-
E.
weaponUsedOnSelf
Indicates that an entity uses a weapon against itself, causing self-directed harm or attack.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f314fc81908a65eec389e8b1fb |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:11 p.m.