Triple
T31916931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Scribonius Libo (consul 16 AD) |
E814856
|
entity |
| Predicate | legal consequence after death |
P126199
|
FINISHED |
| Object | property confiscation |
—
|
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: property confiscation | Statement: [Lucius Scribonius Libo (consul 16 AD), legal consequence after death, property confiscation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legal consequence after death Context triple: [Lucius Scribonius Libo (consul 16 AD), legal consequence after death, property confiscation]
-
A.
deathAfterDeposition
Indicates that one entity dies at some point after another entity has been deposed or removed from a position.
-
B.
continuedAfterDeathOf
Indicates that an action, state, or process persisted beyond and despite the death of a specified entity.
-
C.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
D.
afterDeathOf
chosen
Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified entity.
-
E.
consequenceOfKilling
Indicates that one event or state occurs as a direct result of an act of killing.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:02 a.m.