Triple
T32423361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bungeishunjū |
E828512
|
entity |
| Predicate | hasSubsidiaryOrImprint |
P81839
|
FINISHED |
| Object | Bunshun Bunko |
—
|
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: Bunshun Bunko | Statement: [Bungeishunjū, hasSubsidiaryOrImprint, Bunshun Bunko]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsidiaryOrImprint Context triple: [Bungeishunjū, hasSubsidiaryOrImprint, Bunshun Bunko]
-
A.
hasParentImprint
Indicates that one publishing imprint is the parent or controlling imprint of another imprint.
-
B.
hasSubsidiaryLabel
Indicates that one entity is identified as a subsidiary or subordinate organization of another entity.
-
C.
hasSubsidiariesIn
Indicates that an entity has subsidiary companies or organizations operating or registered in a specified location or jurisdiction.
-
D.
hasSubsidiaryTitle
Indicates that an entity has an additional or secondary title formally associated with its main title.
-
E.
hasSubImprint
chosen
Indicates that one imprint functions as a subordinate or subsidiary imprint under another imprint.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: May 1, 2026, 12:54 a.m.