Triple
T4808892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugo Drax |
E107015
|
entity |
| Predicate | deathInFilm |
P36869
|
FINISHED |
| Object | ejected into space from airlock |
—
|
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: ejected into space from airlock | Statement: [Hugo Drax, deathInFilm, ejected into space from airlock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathInFilm Context triple: [Hugo Drax, deathInFilm, ejected into space from airlock]
-
A.
deathInFiction
chosen
Indicates that an entity’s death occurs within a fictional work or narrative rather than in real life.
-
B.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
C.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
D.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
E.
deathDescribedAs
Indicates that one entity characterizes, portrays, or refers to another entity’s death using a particular description, metaphor, or wording.
- 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_69bd43f779448190b92885cb70abb6c2 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.