Triple
T24517845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human, Volume 2 |
E606423
|
entity |
| Predicate | storyProgression |
P59803
|
FINISHED |
| Object | continues plot from first volume |
—
|
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: continues plot from first volume | Statement: [Human, Volume 2, storyProgression, continues plot from first volume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyProgression Context triple: [Human, Volume 2, storyProgression, continues plot from first volume]
-
A.
storyStatus
Indicates the current state or phase of a story within its lifecycle (e.g., planned, in progress, completed, or archived).
-
B.
storyNumber
Indicates the numerical identifier assigned to a specific story within a collection, sequence, or dataset.
-
C.
storyEngine
Indicates that one entity functions as a narrative-generating or plot-controlling mechanism for another entity or set of events.
-
D.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
E.
narrativeSequence
chosen
Indicates that one event or narrative element follows another in a temporal or logical storytelling order.
- 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.