Triple

T16378866
Position Surface form Disambiguated ID Type / Status
Subject The Lake House E397746 entity
Predicate hasGoodreadsID P28753 FINISHED
Object 22341263 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: 22341263 | Statement: [The Lake House, hasGoodreadsID, 22341263]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGoodreadsID
Context triple: [The Lake House, hasGoodreadsID, 22341263]
  • A. hasGoodreadsId chosen
    Indicates that an entity is associated with a specific identifier used by Goodreads to uniquely reference it in their system.
  • B. hasGoodreadsWorkId
    Indicates that an entity is associated with a specific Goodreads work identifier linking it to a work entry in the Goodreads database.
  • C. hasBook
    Indicates that an entity possesses, owns, or is associated with a particular book.
  • D. bookMention
    Indicates that one entity (such as a text, person, or source) makes reference to or cites a particular book.
  • E. containsBook
    Indicates that one entity (typically a container or collection) includes a specific book as part of its contents.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e319da3c6c8190a9ccf744996c31e8 completed April 18, 2026, 5:42 a.m.
PD Predicate disambiguation batch_69e226f94dd48190b7b8e0e983738a67 completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:08 a.m.