Triple
T8561921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars spin-off films |
E202709
|
entity |
| Predicate | followsStoryStructure |
P68374
|
FINISHED |
| Object | self-contained plots |
—
|
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: self-contained plots | Statement: [Star Wars spin-off films, followsStoryStructure, self-contained plots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsStoryStructure Context triple: [Star Wars spin-off films, followsStoryStructure, self-contained plots]
-
A.
followsStoryOf
Indicates that one narrative, account, or storyline continues from, is based on, or is derived from the events or structure of another.
-
B.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
C.
narrativeSequence
Indicates that one event or narrative element follows another in a temporal or logical storytelling order.
-
D.
narrativeStrategy
chosen
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
-
E.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe94c0c3c8190aca981c07b090dc0 |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.