Triple
T10210963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Painted House |
E242324
|
entity |
| Predicate | firstEditionIsbn |
P74471
|
FINISHED |
| Object | 978-0-385-50403-8 |
—
|
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-385-50403-8 | Statement: [A Painted House, firstEditionIsbn, 978-0-385-50403-8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionIsbn Context triple: [A Painted House, firstEditionIsbn, 978-0-385-50403-8]
-
A.
firstEditionISBN
chosen
Indicates that the object is the International Standard Book Number (ISBN) assigned to the first edition of the subject work.
-
B.
firstEditionType
Indicates that an entity is classified as a first edition of a work, specifying the type or category of that first edition.
-
C.
isbnFirstEnglishEdition
Indicates that the object is the ISBN identifier corresponding to the first English-language edition of the subject work.
-
D.
firstEditionPublicationYear
Indicates the year in which an entity’s first edition was originally published.
-
E.
firstEditionResult
Indicates that one entity is the outcome, record, or result associated specifically with the first edition of another entity.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa22071c819095febd18dd607978 |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:01 a.m.