Triple
T30598079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultimate End (2015) |
E778837
|
entity |
| Predicate | mergesUniverseWith |
P77
|
FINISHED |
| Object | mainstream Marvel Universe |
—
|
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: mainstream Marvel Universe | Statement: [Ultimate End (2015), mergesUniverseWith, mainstream Marvel Universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergesUniverseWith Context triple: [Ultimate End (2015), mergesUniverseWith, mainstream Marvel Universe]
-
A.
mergedInto
chosen
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
B.
setInUniverse
Indicates that something is located within, belongs to, or takes place in a particular fictional or conceptual universe.
-
C.
setInUniverseDuring
Indicates that an event, story, or situation takes place within a particular universe during a specified time or period.
-
D.
linkedToUniversePhase
Indicates that something is associated or connected to a particular phase or stage of the universe’s evolution or lifecycle.
-
E.
inUniverseMaker
Indicates that an entity exists or occurs within the fictional universe created or defined 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:24 p.m.