Triple
T36853300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvel Nemesis: Rise of the Imperfects |
E910725
|
entity |
| Predicate | tieInPublisher |
P141466
|
FINISHED |
| Object | Marvel Comics |
—
|
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 Comics | Statement: [Marvel Nemesis: Rise of the Imperfects, tieInPublisher, Marvel Comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieInPublisher Context triple: [Marvel Nemesis: Rise of the Imperfects, tieInPublisher, Marvel Comics]
-
A.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
B.
publisherAssociatedWith
chosen
Indicates a relationship where a publisher is connected or linked to another entity, such as by publishing, distributing, or otherwise being involved with its content or materials.
-
C.
coPublisher
Indicates that two or more entities jointly publish the same work or content.
-
D.
winnerPublisher
Indicates that a publisher is the one associated with or responsible for the winning entry, work, or outcome in a given contest or award.
-
E.
publisherType
Indicates the classification or category of a publisher in relation to a published work or 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.