Triple

T14860582
Position Surface form Disambiguated ID Type / Status
Subject And Can It Be That I Should Gain? E349475 entity
Predicate approximateYearOfComposition P114755 FINISHED
Object 1738 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: 1738 | Statement: [And Can It Be That I Should Gain?, approximateYearOfComposition, 1738]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approximateYearOfComposition
Context triple: [And Can It Be That I Should Gain?, approximateYearOfComposition, 1738]
  • A. approximateYearWritten chosen
    Indicates the estimated calendar year in which something was written, when the exact year is not known.
  • B. probableCenturyOfComposition
    Indicates the century in which something (typically a work or composition) was most likely created or written.
  • C. approximateYearOfCompletion
    Indicates the estimated calendar year in which something was completed, rather than an exact or confirmed year.
  • D. releaseApproximateYear
    Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
  • E. approximateStartYear
    Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
  • 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_69d822ed7e1881909b90fca143ad7e34 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded573cba881908d6d9ac570a64e5f completed April 15, 2026, 12:01 a.m.
PD Predicate disambiguation batch_69de8c1798c08190b433e9ad21e41a42 completed April 14, 2026, 6:48 p.m.
Created at: April 10, 2026, 1:54 a.m.