Triple
T28757078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrysippus |
E731699
|
entity |
| Predicate | deathBlame |
P170404
|
FINISHED |
| Object | Laius was accused by Pelops of corrupting Chrysippus |
—
|
NE NERFINISHED |
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: Laius was accused by Pelops of corrupting Chrysippus | Statement: [Chrysippus, deathBlame, Laius was accused by Pelops of corrupting Chrysippus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathBlame Context triple: [Chrysippus, deathBlame, Laius was accused by Pelops of corrupting Chrysippus]
-
A.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
B.
deathOvers
Indicates the number of overs bowled in the final phase of a limited-overs cricket innings, typically focused on the closing overs where scoring and wicket-taking intensify.
-
C.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
D.
deathResultedIn
Indicates that one event, action, or condition caused or led directly to a particular death as its outcome.
-
E.
deathInterpretedAs
Indicates that one entity’s death is understood, framed, or interpreted in a particular way by another entity or within a given context.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 28, 2026, 6:10 a.m.