Triple
T33581935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPH |
E860170
|
entity |
| Predicate | publisherImprintOwner |
P198973
|
FINISHED |
| Object | Mark Millar |
—
|
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: Mark Millar | Statement: [MPH, publisherImprintOwner, Mark Millar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherImprintOwner Context triple: [MPH, publisherImprintOwner, Mark Millar]
-
A.
publisherImprint
Indicates the publishing imprint or brand under which a work is issued by a publisher.
-
B.
publisherImprintLaterKnownAs
Indicates that a publisher’s imprint was later renamed or became known by a different imprint name.
-
C.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
D.
publisherOfPrintVersion
Indicates that an entity serves as the publisher responsible for the printed (physical) version of another entity.
-
E.
publisherAssociatedWith
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.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
| PDg | Predicate description generation | batch_69ff17bda59c8190b27c524f3e01c6df |
completed | May 9, 2026, 11:17 a.m. |
Created at: May 1, 2026, 1:40 a.m.