Triple
T4757399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telegony |
E105621
|
entity |
| Predicate | continuesStoryOf |
P28389
|
FINISHED |
| Object | Odysseus after his return to Ithaca |
—
|
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: Odysseus after his return to Ithaca | Statement: [Telegony, continuesStoryOf, Odysseus after his return to Ithaca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesStoryOf Context triple: [Telegony, continuesStoryOf, Odysseus after his return to Ithaca]
-
A.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
followsStoryOf
chosen
Indicates that one narrative, account, or storyline continues from, is based on, or is derived from the events or structure of another.
-
D.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
E.
narrativeConnection
Indicates a meaningful relationship between elements within a narrative, such as events, characters, or scenes, that links them in terms of plot, causality, or thematic continuity.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64ec16a0819089836e4388b555f6 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.