Triple
T28674087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill House Comics |
E725812
|
entity |
| Predicate | publisherImprintType |
P2763
|
FINISHED |
| Object | limited-series focused |
—
|
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: limited-series focused | Statement: [Hill House Comics, publisherImprintType, limited-series focused]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherImprintType Context triple: [Hill House Comics, publisherImprintType, limited-series focused]
-
A.
publisherImprint
chosen
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.
distributorImprint
Indicates that one entity serves as the distributing imprint or label responsible for releasing or circulating another entity (such as a work or product).
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 28, 2026, 5:05 a.m.