Triple
T7178924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ring for Jeeves |
E167393
|
entity |
| Predicate | hasISBNModernEdition |
P6687
|
FINISHED |
| Object | 9780099513972 |
—
|
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: 9780099513972 | Statement: [Ring for Jeeves, hasISBNModernEdition, 9780099513972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISBNModernEdition Context triple: [Ring for Jeeves, hasISBNModernEdition, 9780099513972]
-
A.
hasModernEditions
chosen
Indicates that an original work or text has one or more updated or contemporary published editions.
-
B.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
C.
modernEditionBy
Indicates that one entity is a modern edition or updated version that has been prepared, edited, or published by another entity.
-
D.
hasEditionType
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
-
E.
hasYoungReadersEdition
Indicates that a work has a specially adapted edition intended for young or juvenile readers.
- 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_69c6888a7c548190a3d39b52a393080f |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:49 p.m.