Triple
T23898451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Girl in the Spider's Web |
E600970
|
entity |
| Predicate | hasEnglishEditionISBN |
P20928
|
FINISHED |
| Object | 978-0-385-35328-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-35328-8 | Statement: [The Girl in the Spider's Web, hasEnglishEditionISBN, 978-0-385-35328-8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnglishEditionISBN Context triple: [The Girl in the Spider's Web, hasEnglishEditionISBN, 978-0-385-35328-8]
-
A.
hasEnglishEdition
Indicates that one entity has a version or edition of itself that is produced or available in the English language.
-
B.
isbnFirstEnglishEdition
chosen
Indicates that the object is the ISBN identifier corresponding to the first English-language edition of the subject work.
-
C.
EnglishEditionURL
Indicates the web address where the English-language edition or version of an item can be accessed.
-
D.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
E.
EnglishEditionPublicationYear
Indicates the calendar year in which the English-language edition of a work was first published.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cddb3fdc819096dc84a1774d9bee |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.