Triple
T12945102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | final chase of Moby Dick |
E309739
|
entity |
| Predicate | timeOfPublicationOfSourceWork |
P59624
|
FINISHED |
| Object | 1851 |
—
|
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: 1851 | Statement: [final chase of Moby Dick, timeOfPublicationOfSourceWork, 1851]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfPublicationOfSourceWork Context triple: [final chase of Moby Dick, timeOfPublicationOfSourceWork, 1851]
-
A.
periodOfOriginOfSourceWork
Indicates the historical time period during which the original source work was created or first came into existence.
-
B.
epochAtPublication
chosen
Indicates the specific time or epoch at which the publication event occurs or is recorded.
-
C.
relatedWorkPublicationYear
Indicates the year in which a related work associated with the primary entity was published.
-
D.
publicationPeriod
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
E.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
- 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.