Triple
T28969319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinity War (1992) |
E734227
|
entity |
| Predicate | comicLine |
P91477
|
FINISHED |
| Object | Marvel Universe |
—
|
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 Universe | Statement: [Infinity War (1992), comicLine, Marvel Universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comicLine Context triple: [Infinity War (1992), comicLine, Marvel Universe]
-
A.
comicBookUniverse
chosen
Indicates that multiple comic book characters, stories, or events exist within and are governed by the same fictional continuity or shared narrative world.
-
B.
comicPublisher
Indicates that one entity is the publisher responsible for producing or distributing the comic associated with another entity.
-
C.
appearsInSeriesByPublisher
Indicates that an entity appears in a series that is produced or released by a specified publisher.
-
D.
comicTitle
Indicates that one entity is the title or name of a comic associated with another entity.
-
E.
comicEra
Indicates the historical or stylistic period within which a comic was created or is categorized.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65c3001908190a21cfe2d25c319eb |
completed | May 2, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:04 a.m.