Triple

T10462626
Position Surface form Disambiguated ID Type / Status
Subject Lyttelton family E246712 entity
Predicate hasTitle P38 FINISHED
Object Baron Cobham E423678 NE 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: Baron Cobham | Statement: [Lyttelton family, hasTitle, Baron Cobham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baron Cobham
Context triple: [Lyttelton family, hasTitle, Baron Cobham]
  • A. Baron Cobham chosen
    Baron Cobham is a hereditary title in the British peerage historically associated with influential political and military figures in England.
  • B. Baron Camelford
    Baron Camelford is a hereditary title in the British peerage associated with the influential Pitt political family.
  • C. Baron Verulam
    Baron Verulam is the English noble title held by Francis Bacon, the influential Renaissance philosopher, statesman, and pioneer of the scientific method.
  • D. Baron Guilford
    Baron Guilford is a British peerage title historically associated with the North family, notably held by Francis North, 1st Earl of Guilford.
  • E. Baron Clifford
    Baron Clifford is a hereditary title in the Peerage of the United Kingdom historically associated with the aristocratic Cavendish family and the Dukes of Devonshire.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d381c16c248190a2fe5b471e584e9c completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d50884fac48190af22e181b1492557 completed April 7, 2026, 1:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69d90dac584081909a79bc300b9338c8 completed April 10, 2026, 2:48 p.m.
Created at: April 6, 2026, 12:19 p.m.