Triple
T35445350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Return from Cythera |
E1024466
|
entity |
| Predicate | impliesNarrativeOf |
P44225
|
FINISHED |
| Object | departure from Cythera |
—
|
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: departure from Cythera | Statement: [Return from Cythera, impliesNarrativeOf, departure from Cythera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesNarrativeOf Context triple: [Return from Cythera, impliesNarrativeOf, departure from Cythera]
-
A.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
B.
narratesWith
Indicates that one entity tells, recounts, or presents a story, event, or information in conjunction with or alongside another entity.
-
C.
narratesAs
Indicates that one entity tells, recounts, or presents a story, event, or information in the manner, style, or voice of another entity.
-
D.
narrativePremise
chosen
Indicates the foundational situation, conflict, or setup that initiates and drives the narrative’s events.
-
E.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7962095a481909719282611283f4d |
completed | May 3, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.