Triple
T37715180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demon Bear Saga |
E939437
|
entity |
| Predicate | continuesInIssue |
P144022
|
FINISHED |
| Object | The New Mutants #19 |
—
|
NE NERFINISHED |
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: The New Mutants #19 | Statement: [Demon Bear Saga, continuesInIssue, The New Mutants #19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesInIssue Context triple: [Demon Bear Saga, continuesInIssue, The New Mutants #19]
-
A.
continuesOn
Indicates that an action, process, or state persists or carries forward beyond a given point, without interruption or termination.
-
B.
endsInIssue
Indicates that an event, process, or situation concludes with a particular issue or problem as its outcome.
-
C.
continuedPublicationOf
Indicates that a publication or series is being carried on or issued further over time, following an earlier phase or version.
-
D.
continuesInto
chosen
Indicates that one entity extends forward in time, space, or sequence so that it directly proceeds into and forms a continuous progression with another entity.
-
E.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4:18 p.m.