Triple
T25186798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | These Are the Voyages... |
E630738
|
entity |
| Predicate | featuresDeathOfCharacter |
P51826
|
FINISHED |
| Object | Charles "Trip" Tucker III |
—
|
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: Charles "Trip" Tucker III | Statement: [These Are the Voyages..., featuresDeathOfCharacter, Charles "Trip" Tucker III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDeathOfCharacter Context triple: [These Are the Voyages..., featuresDeathOfCharacter, Charles "Trip" Tucker III]
-
A.
featuresDeath
Indicates that the subject includes, depicts, or involves a death or deaths as a notable element.
-
B.
deathInFiction
Indicates that an entity’s death occurs within a fictional work or narrative rather than in real life.
-
C.
containsDeathOf
chosen
Indicates that the subject includes, depicts, or involves the death of the referenced entity.
-
D.
roleInDeaths
Indicates the role or involvement an entity had in causing, contributing to, or being responsible for one or more deaths.
-
E.
facesDeath
Indicates that an entity is confronting, experiencing, or is directly threatened by death or a life-ending situation.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 12:44 p.m.