Triple
T4917965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eteocles |
E110392
|
entity |
| Predicate | aftermathOfDeath |
P48782
|
FINISHED |
| Object | denial of burial to Polynices in some versions |
—
|
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: denial of burial to Polynices in some versions | Statement: [Eteocles, aftermathOfDeath, denial of burial to Polynices in some versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aftermathOfDeath Context triple: [Eteocles, aftermathOfDeath, denial of burial to Polynices in some versions]
-
A.
aftermathOf
chosen
Indicates that one event, state, or condition occurs as a consequence or result following another event.
-
B.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
C.
death
Indicates the event or state in which an entity ceases to live or exist, marking the end of its biological or functional processes.
-
D.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
E.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa760448190946401b4b21ea8b7 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.