Triple

T34914259
Position Surface form Disambiguated ID Type / Status
Subject Philip Stanhope, 1st Earl of Chesterfield E1006957 entity
Predicate parliamentaryServiceBeforeCivilWar P182102 FINISHED
Object yes 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: yes | Statement: [Philip Stanhope, 1st Earl of Chesterfield, parliamentaryServiceBeforeCivilWar, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: parliamentaryServiceBeforeCivilWar
Context triple: [Philip Stanhope, 1st Earl of Chesterfield, parliamentaryServiceBeforeCivilWar, yes]
  • A. parliamentaryService
    Indicates that an entity serves or has served as a member within a parliamentary body or legislature.
  • B. parliamentaryBodyBefore1707
    Indicates that one parliamentary body existed and functioned prior to the year 1707.
  • C. parliamentaryServiceStart
    Indicates the date or point in time when an entity’s service in a parliamentary role or body begins.
  • D. parliamentaryEra
    Indicates the historical period or era during which a particular parliament or parliamentary system was in effect.
  • E. hasParliamentaryHistory
    Indicates that an entity possesses a record or background of involvement, activity, or events within a parliamentary context.
  • 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_69f76dc2b6b0819095a61debbd405269 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78710282c81909146dc0be91e983f completed May 3, 2026, 5:34 p.m.
PD Predicate disambiguation batch_69f784162134819098413482ef52042f completed May 3, 2026, 5:21 p.m.
PDg Predicate description generation batch_69f7870dfe108190996c0c68630edc7f completed May 3, 2026, 5:34 p.m.
Created at: May 3, 2026, 4 p.m.