Triple
T17354031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graham Kerr |
E421887
|
entity |
| Predicate | hasBibliographyType |
P10719
|
FINISHED |
| Object | cookbooks |
—
|
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: cookbooks | Statement: [Graham Kerr, hasBibliographyType, cookbooks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBibliographyType Context triple: [Graham Kerr, hasBibliographyType, cookbooks]
-
A.
hasBibliography
Indicates that one entity includes or is associated with a bibliography listing referenced or related works.
-
B.
hasBibliographicCategory
chosen
Indicates that an entity is associated with a specific bibliographic classification or category within a cataloging or documentation system.
-
C.
hasGenreInBibliography
Indicates that a work’s bibliography includes sources belonging to a specified genre.
-
D.
bibliographicContribution
Indicates that an entity has contributed to the creation, authorship, or production of a bibliographic resource (such as a book, article, or other documented work).
-
E.
hasCitationSystem
Indicates that one entity uses, follows, or is governed by a particular citation or referencing system defined by 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2e660c81908700aed5c42e9043 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.