Triple
T31323970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batman: Hush |
E798828
|
entity |
| Predicate | storyArcLengthIssues |
P115001
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [Batman: Hush, storyArcLengthIssues, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyArcLengthIssues Context triple: [Batman: Hush, storyArcLengthIssues, 12]
-
A.
storyArcLength
Indicates the duration or extent of a narrative arc within a story, such as how long a particular plotline continues.
-
B.
storyArcStart
Indicates the point in a narrative where a particular story arc or plotline begins.
-
C.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
D.
problemInPlot
chosen
Indicates that there is an issue, flaw, or inconsistency present within the structure or progression of a plot.
-
E.
linkedCharacterArc
Indicates that one character’s narrative development is directly connected to, influenced by, or dependent on another character’s arc.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 9:15 p.m.