Triple
T36603185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakespeare’s Henry VI plays |
E902972
|
entity |
| Predicate | narrativePrequelTo |
P47760
|
FINISHED |
| Object | Richard III |
—
|
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: Richard III | Statement: [Shakespeare’s Henry VI plays, narrativePrequelTo, Richard III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativePrequelTo Context triple: [Shakespeare’s Henry VI plays, narrativePrequelTo, Richard III]
-
A.
isPrequelTo
chosen
Indicates that one work or event occurs earlier in time and narratively sets up or leads into another work or event.
-
B.
prequelOrSequelTo
Indicates that one work in a narrative series occurs earlier or later in the storyline or release order relative to another work, as its prequel or sequel.
-
C.
narrativeTimeGapFromPrequel
Indicates that there is a temporal gap in the story’s timeline between this work and its prequel.
-
D.
narrativeSequenceBefore
Indicates that one narrative event or element occurs earlier in the story’s sequence than another.
-
E.
narrativePremise
Indicates the foundational situation, conflict, or setup that initiates and drives the narrative’s events.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:11 p.m.