Triple
T24207271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster |
E600434
|
entity |
| Predicate | ISBNType |
P39051
|
FINISHED |
| Object | tankobon volumes published by Shogakukan |
—
|
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: tankobon volumes published by Shogakukan | Statement: [Monster, ISBNType, tankobon volumes published by Shogakukan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISBNType Context triple: [Monster, ISBNType, tankobon volumes published by Shogakukan]
-
A.
isbnType
chosen
Indicates the specific classification or format type associated with an ISBN identifier for a publication.
-
B.
isbn
Indicates that a publication is associated with a specific International Standard Book Number (ISBN) that uniquely identifies it.
-
C.
isbn13
Indicates that the subject has the specified 13-digit International Standard Book Number (ISBN-13) as its unique identifier.
-
D.
libraryType
Indicates the specific category or classification of a library based on its function, scope, or organizational role.
-
E.
isbnFirstEnglishEdition
Indicates that the object is the ISBN identifier corresponding to the first English-language edition of the subject work.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f27ca717e8819093fdc82fa063d9a6 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:44 p.m.