Triple
T2277471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Behind the Cloud |
E51203
|
entity |
| Predicate | ISBN-10 |
P1469
|
FINISHED |
| Object | 0470521163 |
—
|
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: 0470521163 | Statement: [Behind the Cloud, ISBN-10, 0470521163]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISBN-10 Context triple: [Behind the Cloud, ISBN-10, 0470521163]
-
A.
isbn13
Indicates that the subject has the specified 13-digit International Standard Book Number (ISBN-13) as its unique identifier.
-
B.
isbn
chosen
Indicates that a publication is associated with a specific International Standard Book Number (ISBN) that uniquely identifies it.
-
C.
isbnFirstEnglishEdition
Indicates that the object is the ISBN identifier corresponding to the first English-language edition of the subject work.
-
D.
deweyDecimalClassification
Indicates the Dewey Decimal System classification assigned to an item, expressing its subject-based placement within a library’s organizational scheme.
-
E.
firstEditionType
Indicates that an entity is classified as a first edition of a work, specifying the type or category of that first edition.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc1ee22988190b7fa28b0b62e8668 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.