Triple
T19069717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wandering Rocks |
E466759
|
entity |
| Predicate | titleAllusionSource |
P117121
|
FINISHED |
| Object | Scylla and Charybdis episode of the Odyssey |
—
|
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: Scylla and Charybdis episode of the Odyssey | Statement: [The Wandering Rocks, titleAllusionSource, Scylla and Charybdis episode of the Odyssey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleAllusionSource Context triple: [The Wandering Rocks, titleAllusionSource, Scylla and Charybdis episode of the Odyssey]
-
A.
titleAlludesTo
Indicates that one title makes an indirect or suggestive reference to the content, theme, or another work associated with the other.
-
B.
nameAllusion
Indicates that one entity’s name is derived from, references, or alludes to another entity.
-
C.
sourceOfTitle
chosen
Indicates that one entity is the origin or provider of another entity’s title or designation.
-
D.
containsAllusion
Indicates that one entity includes or incorporates an indirect reference or allusion to another entity.
-
E.
titleInSources
Indicates that a specific title for an entity is attested or recorded in one or more external sources.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19caa708190876a2cb06aa0c9cc |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.