Triple
T8612443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Curator |
E203942
|
entity |
| Predicate | hasISBNType |
P39051
|
FINISHED |
| Object | ISBN-13 |
—
|
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: ISBN-13 | Statement: [The Curator, hasISBNType, ISBN-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISBNType Context triple: [The Curator, hasISBNType, ISBN-13]
-
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.
containsBook
Indicates that one entity (typically a container or collection) includes a specific book as part of its contents.
-
E.
libraryType
Indicates the specific category or classification of a library based on its function, scope, or organizational role.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fdf21c81908ffc6363e98ab871 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.