Triple
T1199976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinbad the Sailor |
E25756
|
entity |
| Predicate | storyStructure |
P24126
|
FINISHED |
| Object | series of episodic voyages |
—
|
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: series of episodic voyages | Statement: [Sinbad the Sailor, storyStructure, series of episodic voyages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyStructure Context triple: [Sinbad the Sailor, storyStructure, series of episodic voyages]
-
A.
storyline
chosen
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
B.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
textualStructure
Indicates how parts of a text are organized and related to each other within its overall structure.
-
E.
narrativePassage
Indicates that a segment of text functions as a narrative passage, conveying events, actions, or storytelling rather than exposition, dialogue, or other discourse types.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9ec3488190afe35af54efae5e9 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.