Triple
T10400447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1 Henry IV |
E245130
|
entity |
| Predicate | containsSubplot |
P19975
|
FINISHED |
| Object | comic exploits of Sir John Falstaff |
—
|
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: comic exploits of Sir John Falstaff | Statement: [1 Henry IV, containsSubplot, comic exploits of Sir John Falstaff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSubplot Context triple: [1 Henry IV, containsSubplot, comic exploits of Sir John Falstaff]
-
A.
hasSubplot
chosen
Indicates that a narrative work contains a secondary, subordinate storyline in addition to its main plot.
-
B.
hasSubscene
Indicates that a scene is composed of or contains another scene as a subordinate or nested part.
-
C.
containsPlayWithinPlay
Indicates that one play or dramatic work includes another play performed or depicted within its own narrative.
-
D.
containsSubchapter
Indicates that one chapter or section includes another, more specific subchapter as a part of its structure.
-
E.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9e2f11c8190b30695cba2975544 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:07 p.m.