Triple
T23481899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crate |
E570426
|
entity |
| Predicate | notableDeathMethod |
P152545
|
FINISHED |
| Object | victims devoured by creature from crate |
—
|
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: victims devoured by creature from crate | Statement: [The Crate, notableDeathMethod, victims devoured by creature from crate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDeathMethod Context triple: [The Crate, notableDeathMethod, victims devoured by creature from crate]
-
A.
notableDeath
Indicates that an entity’s death is considered significant or noteworthy in some context.
-
B.
notableDeathTollEvent
Indicates that an event is characterized by causing an unusually large or historically significant number of deaths.
-
C.
notableBearerDeathYear
Indicates the year in which a notable bearer of the referenced name, title, or role died.
-
D.
notableBirth
Indicates that one entity is the place or context in which another entity was born, highlighting a notable birth event.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a75118048190b4af687906c4e747 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:03 p.m.