Triple

T30263525
Position Surface form Disambiguated ID Type / Status
Subject House of Spencer E769568 entity
Predicate hasNotableMember P304 FINISHED
Object Henry Spencer of Althorp
Henry Spencer of Althorp was an English nobleman and early member of the prominent Spencer family associated with the Althorp estate.
E1918068 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 Spencer of Althorp | Statement: [House of Spencer, hasNotableMember, Henry Spencer of Althorp]
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 Spencer of Althorp
Triple: [House of Spencer, hasNotableMember, Henry Spencer of Althorp]
Generated description
Henry Spencer of Althorp was an English nobleman and early member of the prominent Spencer family associated with the Althorp estate.

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_69f22484a5f48190b678cd607700bc82 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f680ab3ba481908d75676fef98820f completed May 2, 2026, 10:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27ac04e2948190a1a71bcb65d912d5 completed June 9, 2026, 6 a.m.
NEDg Description generation batch_6a27ad769f8c81908ffbc1edbb85bbf0 completed June 9, 2026, 6:06 a.m.
NED2 Entity disambiguation (via description) batch_6a27adf304f4819087f621c34447de0f completed June 9, 2026, 6:08 a.m.
Created at: April 29, 2026, 7:42 p.m.