Triple
T26825992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cú Chulainn |
E675377
|
entity |
| Predicate | deathDetail |
P138528
|
FINISHED |
| Object | tied himself to a standing stone to die on his feet |
—
|
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: tied himself to a standing stone to die on his feet | Statement: [Cú Chulainn, deathDetail, tied himself to a standing stone to die on his feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathDetail Context triple: [Cú Chulainn, deathDetail, tied himself to a standing stone to die on his feet]
-
A.
deathDetails
chosen
Indicates the specific circumstances, causes, and contextual information associated with an entity’s death.
-
B.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
-
C.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
D.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
E.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 4:58 a.m.