Triple

T38298267
Position Surface form Disambiguated ID Type / Status
Subject Robert de Stuteville E1032153 entity
Predicate nobleFamily P914 FINISHED
Object Stuteville family
The Stuteville family was a prominent Anglo-Norman noble lineage influential in medieval England and associated with figures such as Robert de Stuteville.
E2263736 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: Stuteville family | Statement: [Robert de Stuteville, nobleFamily, Stuteville family]
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: Stuteville family
Triple: [Robert de Stuteville, nobleFamily, Stuteville family]
Generated description
The Stuteville family was a prominent Anglo-Norman noble lineage influential in medieval England and associated with figures such as Robert de Stuteville.

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_69f76e0f2084819091299d021625c3fe completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fcc618020c8190b055d8c8d4d7c050 completed May 7, 2026, 5:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a419e0693308190a380c8d6590d6756 completed June 28, 2026, 10:19 p.m.
NEDg Description generation batch_6a419ed29ed88190b27e65c199ab31a7 completed June 28, 2026, 10:23 p.m.
NED2 Entity disambiguation (via description) batch_6a419f633f00819083f568cde8b0f9d5 completed June 28, 2026, 10:25 p.m.
Created at: May 3, 2026, 4:30 p.m.