Triple
T37715181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demon Bear Saga |
E939437
|
entity |
| Predicate | concludesInIssue |
P141141
|
FINISHED |
| Object | The New Mutants #20 |
—
|
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 #20 | Statement: [Demon Bear Saga, concludesInIssue, The New Mutants #20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludesInIssue Context triple: [Demon Bear Saga, concludesInIssue, The New Mutants #20]
-
A.
concludingIssue
chosen
Indicates that an issue represents the final or closing installment in a sequence, series, or publication run.
-
B.
endsInIssue
Indicates that an event, process, or situation concludes with a particular issue or problem as its outcome.
-
C.
concludesIn
Indicates that an event, process, or action ends or reaches its final state within a specified time, place, or context.
-
D.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
E.
concludes
Indicates that one entity brings something (such as an event, process, or discussion) to an end or reaches a final decision or judgment about it.
- 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_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.