Triple
T33914128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman #13 |
E869402
|
entity |
| Predicate | featuresPublisherImprint |
P2763
|
FINISHED |
| Object | DC Comics |
E18704
|
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: DC Comics | Statement: [Superman #13, featuresPublisherImprint, DC Comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPublisherImprint Context triple: [Superman #13, featuresPublisherImprint, DC Comics]
-
A.
publisherImprint
chosen
Indicates the publishing imprint or brand under which a work is issued by a publisher.
-
B.
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).
-
C.
overseesImprint
Indicates that one entity has managerial or supervisory responsibility over the operations or activities of another entity, typically a subsidiary brand or imprint.
-
D.
includesImprint
Indicates that one entity contains, incorporates, or carries the imprint or branding of another entity.
-
E.
publisherImprintLaterKnownAs
Indicates that a publisher’s imprint was later renamed or became known by a different imprint name.
- F. None of above.
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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0238010fa481909b07a5c22aa0abde |
completed | May 11, 2026, 8:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36823095ac819089a169744f43d075 |
completed | June 20, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_6a0236cfdcb481908323b67b925c76d9 |
completed | May 11, 2026, 8:06 p.m. |
Created at: May 1, 2026, 1:48 a.m.