Triple
T18487857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyberabad Days |
E451735
|
entity |
| Predicate | hasIsbn10 |
P1469
|
FINISHED |
| Object | 1591027443 |
—
|
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: 1591027443 | Statement: [Cyberabad Days, hasIsbn10, 1591027443]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIsbn10 Context triple: [Cyberabad Days, hasIsbn10, 1591027443]
-
A.
isbn13
Indicates that the subject has the specified 13-digit International Standard Book Number (ISBN-13) as its unique identifier.
-
B.
isbnType
Indicates the specific classification or format type associated with an ISBN identifier for a publication.
-
C.
isbn
chosen
Indicates that a publication is associated with a specific International Standard Book Number (ISBN) that uniquely identifies it.
-
D.
hasISBNInCollection
Indicates that a particular ISBN is present within a specified collection of items or works.
-
E.
hasASIN
Indicates that an entity is associated with a specific Amazon Standard Identification Number (ASIN) that uniquely identifies it in Amazon’s catalog.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d8bac4819099306abbf78b9565 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.