Triple

T32840046
Position Surface form Disambiguated ID Type / Status
Subject Duke of Cumberland and Teviotdale E839936 entity
Predicate reasonForAttainder P186165 FINISHED
Object holder fought against the United Kingdom in World War I 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: holder fought against the United Kingdom in World War I | Statement: [Duke of Cumberland and Teviotdale, reasonForAttainder, holder fought against the United Kingdom in World War I]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForAttainder
Context triple: [Duke of Cumberland and Teviotdale, reasonForAttainder, holder fought against the United Kingdom in World War I]
  • A. reasonForConviction
    Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
  • B. punishmentForTreason chosen
    Indicates the specific penalty or consequence imposed on an entity as a result of committing treason.
  • C. timeOfCondemnation
    Indicates the specific time at which a condemnation (such as a legal judgment or formal denunciation) occurs or is issued.
  • D. reasonForMurder
    Indicates the motive or underlying cause that led someone to commit a murder.
  • E. reasonForDeath
    Indicates the cause, circumstance, or condition that led to an entity’s death.
  • 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_69f3493ff0888190b51e974eae2a7834 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fd3a69f1e08190a11aed015bff0858 completed May 8, 2026, 1:20 a.m.
PD Predicate disambiguation batch_69fd39124180819080ca7911d3515d6d completed May 8, 2026, 1:14 a.m.
Created at: May 1, 2026, 1:16 a.m.