Triple
T15608538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Silius |
E375223
|
entity |
| Predicate | legalStatusAtEndOfLife |
P119425
|
FINISHED |
| Object | condemned traitor of the Roman state |
—
|
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: condemned traitor of the Roman state | Statement: [Gaius Silius, legalStatusAtEndOfLife, condemned traitor of the Roman state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusAtEndOfLife Context triple: [Gaius Silius, legalStatusAtEndOfLife, condemned traitor of the Roman state]
-
A.
mortalStatus
Indicates the state or condition of an entity with respect to being mortal, immortal, or otherwise subject to death.
-
B.
isTerminallyIll
Indicates that an entity is suffering from an incurable illness expected to lead to death in the relatively near future.
-
C.
legalStatusEnd
Indicates the point or event at which a previously valid legal status, condition, or arrangement ceases to be in effect.
-
D.
healthStatusBeforeDeath
Indicates the condition or state of an entity’s health immediately prior to its death.
-
E.
deathStatus
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7ec08c8190b3842cf3043aea27 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:13 a.m.