Triple
T33581937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPH |
E860170
|
entity |
| Predicate | firstPublisherUnderImprint |
P205229
|
FINISHED |
| Object | Millarworld |
E244881
|
NE 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: Millarworld | Statement: [MPH, firstPublisherUnderImprint, Millarworld]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublisherUnderImprint Context triple: [MPH, firstPublisherUnderImprint, Millarworld]
-
A.
firstPublisher
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
B.
publisherImprintLaterKnownAs
Indicates that a publisher’s imprint was later renamed or became known by a different imprint name.
-
C.
firstCompleteEditionPublisher
Indicates the publisher responsible for issuing the first complete edition of a work.
-
D.
publisherImprint
Indicates the publishing imprint or brand under which a work is issued by a publisher.
-
E.
originalPublisherType
Indicates the type or category of the entity that first published or released the content.
- F. None of above. chosen
Provenance (5 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a361190203c81909a9da6a1e11a62b9 |
completed | June 20, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:40 a.m.