Triple
T30598101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultimate End (2015) |
E778837
|
entity |
| Predicate | mainContinuity |
P181158
|
FINISHED |
| Object | Marvel multiverse |
—
|
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: Marvel multiverse | Statement: [Ultimate End (2015), mainContinuity, Marvel multiverse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainContinuity Context triple: [Ultimate End (2015), mainContinuity, Marvel multiverse]
-
A.
titleContinuity
Indicates that two works share a continuous or consistent use of the same title across versions, installments, or related contexts.
-
B.
starContinuity
Indicates that there is an unbroken, consistent connection or progression involving a star (or stars) across time, space, or related contexts.
-
C.
primaryContinuityOf
Indicates that one entity serves as the main or principal continuation or extension of another entity in a sequence or process.
-
D.
cultContinuity
Indicates the continuation or persistence of a religious cult’s practices, beliefs, or traditions over time.
-
E.
mainUseContinued
Indicates that the primary use or function of something persists or remains in effect over a subsequent period.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 29, 2026, 8:24 p.m.