Triple

T34409650
Position Surface form Disambiguated ID Type / Status
Subject Bedingfeld family E883218 entity
Predicate hasMember P10 FINISHED
Object Henry Bedingfeld
Henry Bedingfeld was a member of the prominent English recusant Bedingfeld family, historically noted for its Catholic loyalty and involvement in Tudor and Stuart politics.
E2096618 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: Henry Bedingfeld | Statement: [Bedingfeld family, hasMember, Henry Bedingfeld]
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: Henry Bedingfeld
Triple: [Bedingfeld family, hasMember, Henry Bedingfeld]
Generated description
Henry Bedingfeld was a member of the prominent English recusant Bedingfeld family, historically noted for its Catholic loyalty and involvement in Tudor and Stuart politics.

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_69f349c1f2208190a09a489bb8b2719d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f718bf8c38819087f287b5ea01f4d4 completed May 3, 2026, 9:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a371828535c8190868f87e3d641caaa completed June 20, 2026, 10:46 p.m.
NEDg Description generation batch_6a3718c84ee481908c220b2564249159 completed June 20, 2026, 10:48 p.m.
NED2 Entity disambiguation (via description) batch_6a37194fcaf48190b32ef74944391ffc completed June 20, 2026, 10:50 p.m.
Created at: May 1, 2026, 1:59 a.m.