Triple
T2903745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pequod |
E62712
|
entity |
| Predicate | meetsFate |
P24728
|
FINISHED |
| Object | sunk by Moby Dick |
—
|
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: sunk by Moby Dick | Statement: [Pequod, meetsFate, sunk by Moby Dick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsFate Context triple: [Pequod, meetsFate, sunk by Moby Dick]
-
A.
eventualFate
chosen
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
B.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
C.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
D.
meets
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
E.
viewOnFate
Indicates a relationship where one entity holds a particular belief, attitude, or perspective about fate or predestination.
- 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.