Triple
T2903569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queequeg |
E62707
|
entity |
| Predicate | deathStatusAtEnd |
P24966
|
FINISHED |
| Object | presumed dead with crew of the Pequod |
—
|
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: presumed dead with crew of the Pequod | Statement: [Queequeg, deathStatusAtEnd, presumed dead with crew of the Pequod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathStatusAtEnd Context triple: [Queequeg, deathStatusAtEnd, presumed dead with crew of the Pequod]
-
A.
deathStatus
chosen
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
-
B.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
C.
diedWhile
Indicates that one entity ceased to live during the occurrence or performance of another specified event or activity.
-
D.
diesAt
Indicates that an entity ceases to live or exist at a specific time or location.
-
E.
deathBefore
Indicates that one entity’s death occurred earlier in time than another entity’s death.
- 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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abe0b5546c8190852d9a454e41eee6 |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.