Triple

T24024272
Position Surface form Disambiguated ID Type / Status
Subject Hatton family E594907 entity
Predicate hasTitle P38 FINISHED
Object Baron Hatton
Baron Hatton is a hereditary noble title in the Peerage of England historically associated with the prominent Hatton family.
E1611760 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: Baron Hatton | Statement: [Hatton family, hasTitle, Baron Hatton]
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: Baron Hatton
Triple: [Hatton family, hasTitle, Baron Hatton]
Generated description
Baron Hatton is a hereditary noble title in the Peerage of England historically associated with the prominent Hatton family.

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_69e288be2c288190a3a46006945557f7 completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1d769f7248190ae145218fb0e8bbd completed April 29, 2026, 10:03 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f7ea7a15481908302657d545827ae completed May 21, 2026, 9:52 p.m.
NEDg Description generation batch_6a0f7f4ef5e88190b53cdf7135b28cac completed May 21, 2026, 9:55 p.m.
NED2 Entity disambiguation (via description) batch_6a0f7fe13a2481908644e45e96abacce completed May 21, 2026, 9:57 p.m.
Created at: April 17, 2026, 9:53 p.m.