Triple
T14404342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Key to Time |
E357156
|
entity |
| Predicate | storyArcLength |
P114114
|
FINISHED |
| Object | one season |
—
|
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: one season | Statement: [The Key to Time, storyArcLength, one season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyArcLength Context triple: [The Key to Time, storyArcLength, one season]
-
A.
storyNumber
Indicates the numerical identifier assigned to a specific story within a collection, sequence, or dataset.
-
B.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
C.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
D.
stakesInStory
Indicates that one entity has a personal investment, risk, or potential gain/loss tied to the outcome of another entity’s story or narrative.
-
E.
narrativeSequence
Indicates that one event or narrative element follows another in a temporal or logical storytelling order.
- F. None of above. chosen
Provenance (4 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90860ae481908e175decda8624d5 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:17 a.m.