Triple
T216096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Restaurant at the End of the Universe |
E4107
|
entity |
| Predicate | hasGoodreadsWorkId |
P9705
|
FINISHED |
| Object | 8695 |
—
|
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: 8695 | Statement: [The Restaurant at the End of the Universe, hasGoodreadsWorkId, 8695]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoodreadsWorkId Context triple: [The Restaurant at the End of the Universe, hasGoodreadsWorkId, 8695]
-
A.
containsBook
Indicates that one entity (typically a container or collection) includes a specific book as part of its contents.
-
B.
hasCompanionBook
Indicates that one entity (typically a primary work) is associated with another entity that serves as its companion book, providing supplementary or related content.
-
C.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
D.
hasIMDbId
Indicates that an entity is associated with a specific identifier used by the Internet Movie Database (IMDb) to uniquely reference it.
-
E.
hasAudiobookVersion
Indicates that an entity has a corresponding version available in audiobook format.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25dcba5148190ab80fd14c7cf4bb4 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.