Triple

T21581448
Position Surface form Disambiguated ID Type / Status
Subject Venetia Burney E532532 entity
Predicate hasFamilyName P18 FINISHED
Object Burney NE NERFINISHED

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: Burney | Statement: [Venetia Burney, hasFamilyName, Burney]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burney
Context triple: [Venetia Burney, hasFamilyName, Burney]
  • A. Burney chosen
    Burney is an English surname most notably associated with the 18th-century music historian and composer Charles Burney and his literary family.
  • B. Brydges
    Brydges is the surname of a prominent British aristocratic family that included James Brydges, 1st Duke of Chandos, a notable early 18th-century nobleman and patron of the arts.
  • C. Burnes
    Burnes is a surname that functions as a spelling variant of the more common family name Burns.
  • D. Burnard
    Burnard is the ancestral name from which the Scottish Clan Burnett derives its clan name and heritage.
  • E. Beynes
    Beynes is a commune in the Yvelines department of the Île-de-France region in north-central France.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c4618bec8190bcb0feb74568cbb1 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eeeb5c496c819093113dd5790fca48 completed April 27, 2026, 4:51 a.m.
Created at: April 16, 2026, 6:31 p.m.