Triple
T31916912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Scribonius Libo (consul 16 AD) |
E814856
|
entity |
| Predicate | reason for suicide |
P192156
|
FINISHED |
| Object | to avoid condemnation for treason |
—
|
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: to avoid condemnation for treason | Statement: [Lucius Scribonius Libo (consul 16 AD), reason for suicide, to avoid condemnation for treason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reason for suicide Context triple: [Lucius Scribonius Libo (consul 16 AD), reason for suicide, to avoid condemnation for treason]
-
A.
reasonForHusbandSuicide
Indicates the cause, motive, or circumstances that led a husband to take his own life.
-
B.
attemptsSuicide
Indicates that an entity engages in an act intended to end their own life.
-
C.
influencedToSuicideBy
Indicates that one entity’s actions, words, or influence contributed to another entity deciding to commit suicide.
-
D.
killedHimselfAfter
Indicates that an individual committed suicide following a specified event or time.
-
E.
methodOfSuicideAttempt
Indicates the method or means by which a suicide attempt was carried out.
- F. None of above. chosen
Provenance (4 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: May 1, 2026, 12:02 a.m.