Triple

T14664446
Position Surface form Disambiguated ID Type / Status
Subject Marquess of Titchfield E344328 entity
Predicate linkedTitle P914 FINISHED
Object Baron Cirencester E344329 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 Cirencester | Statement: [Marquess of Titchfield, linkedTitle, Baron Cirencester]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baron Cirencester
Context triple: [Marquess of Titchfield, linkedTitle, Baron Cirencester]
  • A. Baron Cirencester chosen
    Baron Cirencester is a British peerage title used as a subsidiary honor by the Duke of Portland.
  • B. Baron Cobham
    Baron Cobham is a hereditary title in the British peerage historically associated with influential political and military figures in England.
  • C. Baron Eddisbury
    Baron Eddisbury is a British peerage title historically associated with the influential Stanley family of Alderley.
  • D. Baron Bridport
    Baron Bridport is a British peerage title historically associated with the naval commander Alexander Hood, 1st Viscount Bridport, and his descendants.
  • E. Baron Sudbury
    Baron Sudbury is a hereditary title in the Peerage of England historically associated with the aristocratic FitzRoy family, descendants of King Charles II.
  • 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_69d822e283fc8190a0e4c235cf880052 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb54ae5ac81908cc69891f280e5f7 completed April 14, 2026, 9:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdd5e4789481909a64622a1d284373 completed May 8, 2026, 12:24 p.m.
Created at: April 10, 2026, 1:27 a.m.