Triple
T14460750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunnm |
E358576
|
entity |
| Predicate | publisher |
P29
|
FINISHED |
| Object | Kodansha |
E775613
|
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: Kodansha | Statement: [Gunnm, publisher, Kodansha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kodansha Context triple: [Gunnm, publisher, Kodansha]
-
A.
Kodansha
chosen
Kodansha is a major Japanese publishing company best known for producing and distributing popular manga, novels, and magazines worldwide.
-
B.
Tokyo Shokonsha
Tokyo Shokonsha was the original name of what is now Yasukuni Shrine, a Shinto shrine in Tokyo dedicated to commemorating Japan’s war dead.
-
C.
Shueisha
Shueisha is a major Japanese publishing company best known for producing popular manga magazines such as Weekly Shōnen Jump.
-
D.
Chūō Kōron Shinsha
Chūō Kōron Shinsha is a major Japanese publishing company known for its influential literary and cultural magazines and books.
-
E.
Bunko-dō publishing house
Bunko-dō publishing house was a Japanese publisher known for its association with prominent literary figures such as poet Yosano Akiko.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91abc1008190a19de4f8f0112c9d |
completed | April 14, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d890be88190afe61dde0d1e75a8 |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 10, 2026, 1:19 a.m.