Triple
T13569463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spellmonger |
E324118
|
entity |
| Predicate | hasContinuingStoryArc |
P39504
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Spellmonger, hasContinuingStoryArc, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContinuingStoryArc Context triple: [Spellmonger, hasContinuingStoryArc, yes]
-
A.
continuesOn
Indicates that an action, process, or state persists or carries forward beyond a given point, without interruption or termination.
-
B.
notableStoryArc
chosen
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
C.
statusInManyContinuities
Indicates that an entity holds a particular status or role across multiple distinct continuities, timelines, or versions of a narrative or system.
-
D.
hasFlashbackStorylines
Indicates that the narrative includes scenes or sequences set in earlier time periods that reveal past events related to the main storyline.
-
E.
continuesFor
Indicates that an event, state, or process persists or remains in effect for a specified duration or period.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00f5b8881908617f42d227ed137 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.