Triple
T12945104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | final chase of Moby Dick |
E309739
|
entity |
| Predicate | concludesArcOf |
P88460
|
FINISHED |
| Object | Ahab’s quest for the white whale |
—
|
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: Ahab’s quest for the white whale | Statement: [final chase of Moby Dick, concludesArcOf, Ahab’s quest for the white whale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludesArcOf Context triple: [final chase of Moby Dick, concludesArcOf, Ahab’s quest for the white whale]
-
A.
concludes
Indicates that one entity brings something (such as an event, process, or discussion) to an end or reaches a final decision or judgment about it.
-
B.
concludesAbout
Indicates that one entity forms or states a conclusion regarding another entity or its properties.
-
C.
concludesStoryOf
chosen
Indicates that one entity brings the narrative or storyline of another entity to an end.
-
D.
concludedWith
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
-
E.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.