Triple
T30344319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monthly Shōnen Gangan |
E771832
|
entity |
| Predicate | publisherIndustry |
P74098
|
FINISHED |
| Object | video game industry |
—
|
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: video game industry | Statement: [Monthly Shōnen Gangan, publisherIndustry, video game industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherIndustry Context triple: [Monthly Shōnen Gangan, publisherIndustry, video game industry]
-
A.
publishingSector
chosen
Indicates a relationship where an entity operates in, is associated with, or belongs to the publishing industry or market segment.
-
B.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
C.
publisherParentCompany
Indicates that one company serves as the parent (owning or controlling) company of a given publisher.
-
D.
publisherProgram
Indicates a program or initiative operated by a publisher that manages or governs its relationships, activities, or offerings with participating entities.
-
E.
publisherImprint
Indicates the publishing imprint or brand under which a work is issued by a publisher.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 29, 2026, 7:55 p.m.