Triple
T25157122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keepsakes and Treasures |
E626343
|
entity |
| Predicate | includedInAudiobook |
P5168
|
FINISHED |
| Object | Fragile Things audiobook |
—
|
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: Fragile Things audiobook | Statement: [Keepsakes and Treasures, includedInAudiobook, Fragile Things audiobook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInAudiobook Context triple: [Keepsakes and Treasures, includedInAudiobook, Fragile Things audiobook]
-
A.
includedInBook
Indicates that something (such as a section, chapter, or content item) is contained within or forms part of a specific book.
-
B.
includedInGenreDefiningWork
Indicates that one entity is part of, or contributes to, a work that is considered foundational or defining for a particular genre.
-
C.
audibleIn
Indicates that a sound produced by one entity can be heard within the spatial or contextual range of another entity.
-
D.
includedInEdition
Indicates that one item (such as a work, text, or component) is contained within or forms part of a particular edition.
-
E.
hasAudiobookVersion
chosen
Indicates that an entity has a corresponding version available in audiobook format.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 18, 2026, 6:30 a.m.