Triple

T31332594
Position Surface form Disambiguated ID Type / Status
Subject Viscount Buxton E799073 entity
Predicate hasNotableHolder P1918 FINISHED
Object Rupert Buxton, 2nd Viscount Buxton
Rupert Buxton, 2nd Viscount Buxton, was a British peer and aristocrat who inherited the viscountcy in the early 20th century.
E1968681 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: Rupert Buxton, 2nd Viscount Buxton | Statement: [Viscount Buxton, hasNotableHolder, Rupert Buxton, 2nd Viscount Buxton]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Rupert Buxton, 2nd Viscount Buxton
Triple: [Viscount Buxton, hasNotableHolder, Rupert Buxton, 2nd Viscount Buxton]
Generated description
Rupert Buxton, 2nd Viscount Buxton, was a British peer and aristocrat who inherited the viscountcy in the early 20th century.

Provenance (5 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_69f224e3f6ac8190a13488516abca7c9 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69ee159b48190b25e7ed6c40948ad completed May 3, 2026, 1:03 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b561bae98819096053ff5dfd0cf63 completed June 12, 2026, 12:43 a.m.
NEDg Description generation batch_6a2b582d76f48190a79f766548d7292e completed June 12, 2026, 12:51 a.m.
NED2 Entity disambiguation (via description) batch_6a2b58de3f5c819098fdc0a6922670a1 completed June 12, 2026, 12:54 a.m.
Created at: April 29, 2026, 9:16 p.m.