Triple

T32808564
Position Surface form Disambiguated ID Type / Status
Subject Earls of Derwentwater E839082 entity
Predicate titleForfeitedIn P73248 FINISHED
Object 1716 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: 1716 | Statement: [Earls of Derwentwater, titleForfeitedIn, 1716]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: titleForfeitedIn
Context triple: [Earls of Derwentwater, titleForfeitedIn, 1716]
  • A. titleForfeited chosen
    Indicates that an entity has lost or been stripped of a title or formal designation it previously held.
  • B. titleAfterSurrender
    Indicates that one entity holds a title or designation that was granted or recognized only after a surrender, capitulation, or yielding event involving another entity.
  • C. titleHolderLoses
    Indicates that an entity who currently holds a title or championship loses that title to another entity.
  • D. forfeitedBy
    Indicates that something (such as a right, claim, or asset) is lost or given up as a consequence of the actions or failure of a particular entity.
  • E. forfeitedTo
    Indicates that something previously held by one party has been lost or surrendered and transferred in ownership, control, or rights to another party, often as a penalty or consequence.
  • 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_69f3493d35208190b4351b4e85f2fa16 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fed48d8e148190a99c0aea29f8a3ee completed May 9, 2026, 6:30 a.m.
PD Predicate disambiguation batch_69fed3c82a24819095e614e31ac0307f completed May 9, 2026, 6:27 a.m.
Created at: May 1, 2026, 1:15 a.m.