Triple
T12945063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | final chase of Moby Dick |
E309739
|
entity |
| Predicate | occursInChapters |
P36548
|
FINISHED |
| Object | Moby-Dick chapters 133–135 |
—
|
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: Moby-Dick chapters 133–135 | Statement: [final chase of Moby Dick, occursInChapters, Moby-Dick chapters 133–135]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInChapters Context triple: [final chase of Moby Dick, occursInChapters, Moby-Dick chapters 133–135]
-
A.
containsChapter
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
B.
foundInChapter
chosen
Indicates that something (such as a concept, section, or element) is contained within or occurs in a specific chapter.
-
C.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another entity.
-
D.
occurredIn
Indicates that an event or action took place within a specific location, context, or time frame.
-
E.
basedOnChapter
Indicates that something (such as a work, section, or element) is derived from, adapted from, or primarily informed by a specific chapter.
- 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.