Triple
T25201563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Too Old to Die Young |
E631136
|
entity |
| Predicate | narrativePacing |
P68374
|
FINISHED |
| Object | slow-burn |
—
|
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: slow-burn | Statement: [Too Old to Die Young, narrativePacing, slow-burn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativePacing Context triple: [Too Old to Die Young, narrativePacing, slow-burn]
-
A.
narrativeStrategy
chosen
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
-
B.
narrativeLength
Indicates the length or extent of a narrative, such as its duration, word count, or overall size.
-
C.
narrativeEffect
Indicates how one event, action, or element in a story influences the progression, tone, or interpretation of the overall narrative.
-
D.
timeOfNarrative
Indicates the specific time or period during which the events of a narrative are set or unfold.
-
E.
narrativeParallel
Indicates that two or more narrative elements (such as storylines, scenes, or character arcs) are structured or progress in a similar, mirrored, or contrasting way to highlight connections between them.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 12:51 p.m.