Triple
T3728769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snow (novel) |
E79010
|
entity |
| Predicate | isbnEnglishEdition |
P1469
|
FINISHED |
| Object | 978-0-375-70403-0 |
—
|
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: 978-0-375-70403-0 | Statement: [Snow (novel), isbnEnglishEdition, 978-0-375-70403-0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isbnEnglishEdition Context triple: [Snow (novel), isbnEnglishEdition, 978-0-375-70403-0]
-
A.
isbnFirstEnglishEdition
Indicates that the object is the ISBN identifier corresponding to the first English-language edition of the subject work.
-
B.
hasEnglishEdition
Indicates that one entity has a version or edition of itself that is produced or available in the English language.
-
C.
isbn
chosen
Indicates that a publication is associated with a specific International Standard Book Number (ISBN) that uniquely identifies it.
-
D.
EnglishEditionPublicationYear
Indicates the calendar year in which the English-language edition of a work was first published.
-
E.
isbnType
Indicates the specific classification or format type associated with an ISBN identifier for a publication.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb17432881909390284b935ed3fd |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.