Triple
T33591846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odyssey (Russian adaptation) |
E860445
|
entity |
| Predicate | hasStoryOrigin |
P133186
|
FINISHED |
| Object | British original series format |
—
|
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: British original series format | Statement: [Odyssey (Russian adaptation), hasStoryOrigin, British original series format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStoryOrigin Context triple: [Odyssey (Russian adaptation), hasStoryOrigin, British original series format]
-
A.
hasNarrativeOrigin
Indicates that something originates from, is derived from, or is based on a particular narrative or story.
-
B.
hasOriginStoryLocation
Indicates that an entity’s origin story takes place at or is associated with a specific location.
-
C.
hasOriginalStory
chosen
Indicates that one entity serves as the original narrative source or story upon which the other entity is based or derived.
-
D.
originStoryIncludes
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
-
E.
hasTraditionalStory
Indicates that one entity possesses, is associated with, or is the source or subject of a traditional story related to the other entity.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:40 a.m.