Triple
T28520009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmo Blatch |
E721733
|
entity |
| Predicate | storyUniverse |
P110803
|
FINISHED |
| Object | Shawshank Redemption universe |
—
|
NE NERFINISHED |
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: Shawshank Redemption universe | Statement: [Elmo Blatch, storyUniverse, Shawshank Redemption universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyUniverse Context triple: [Elmo Blatch, storyUniverse, Shawshank Redemption universe]
-
A.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
B.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
-
C.
hasNarrativeUniverse
chosen
Indicates that one entity exists within, or is part of the fictional world or narrative setting defined by another entity.
-
D.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
E.
fictionalUniverseEvent
Indicates an event or occurrence that takes place within a specific fictional universe or narrative continuity.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 3:20 a.m.