Triple
T6920453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love, Loss, and What We Ate |
E160168
|
entity |
| Predicate | ISBN_13 |
P3840
|
FINISHED |
| Object | 9780062207735 |
—
|
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: 9780062207735 | Statement: [Love, Loss, and What We Ate, ISBN_13, 9780062207735]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISBN_13 Context triple: [Love, Loss, and What We Ate, ISBN_13, 9780062207735]
-
A.
isbn13
chosen
Indicates that the subject has the specified 13-digit International Standard Book Number (ISBN-13) as its unique identifier.
-
B.
isbn
Indicates that a publication is associated with a specific International Standard Book Number (ISBN) that uniquely identifies it.
-
C.
isbnType
Indicates the specific classification or format type associated with an ISBN identifier for a publication.
-
D.
isbnFirstEnglishEdition
Indicates that the object is the ISBN identifier corresponding to the first English-language edition of the subject work.
-
E.
hasGoodreadsId
Indicates that an entity is associated with a specific identifier used by Goodreads to uniquely reference it in their system.
- 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9fa452c8190b2bea2d47309c889 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.