Triple
T2855243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedallah |
E63183
|
entity |
| Predicate | foretells |
P786
|
FINISHED |
| Object | that Ahab will die only after seeing two hearses |
—
|
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: that Ahab will die only after seeing two hearses | Statement: [Fedallah, foretells, that Ahab will die only after seeing two hearses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foretells Context triple: [Fedallah, foretells, that Ahab will die only after seeing two hearses]
-
A.
anticipates
chosen
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
-
B.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
C.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular entity.
-
D.
preludeTo
Indicates that one event, action, or state occurs earlier and serves as an introduction or lead-in to another.
-
E.
eventualFate
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf60852c8190b66c8719c63a723e |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.