Triple
T32261303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woman in the Dunes |
E824157
|
entity |
| Predicate | hasISBNAdaptation |
P176363
|
FINISHED |
| Object | The Woman in the Dunes (novel) |
—
|
NE NERFINISHED |
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: The Woman in the Dunes (novel) | Statement: [Woman in the Dunes, hasISBNAdaptation, The Woman in the Dunes (novel)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISBNAdaptation Context triple: [Woman in the Dunes, hasISBNAdaptation, The Woman in the Dunes (novel)]
-
A.
isbnType
Indicates the specific classification or format type associated with an ISBN identifier for a publication.
-
B.
hasAlternateEditionISBN
Indicates that one edition of a work is linked to another edition of the same work via its alternate ISBN.
-
C.
isbn13
Indicates that the subject has the specified 13-digit International Standard Book Number (ISBN-13) as its unique identifier.
-
D.
hasISMN
Indicates that a musical publication is associated with a specific International Standard Music Number (ISMN) identifier.
-
E.
isbn
Indicates that a publication is associated with a specific International Standard Book Number (ISBN) that uniquely identifies it.
- F. None of above. chosen
Provenance (4 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 12:41 a.m.