Triple

T38210787
Position Surface form Disambiguated ID Type / Status
Subject Goblin Ha' E1010534 entity
Predicate ownershipHistory P22003 FINISHED
Object Hay family of Yester
The Hay family of Yester was a prominent Scottish noble lineage associated with the Earls of Tweeddale and long-established estates in East Lothian.
E2261353 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: Hay family of Yester | Statement: [Goblin Ha', ownershipHistory, Hay family of Yester]
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: Hay family of Yester
Triple: [Goblin Ha', ownershipHistory, Hay family of Yester]
Generated description
The Hay family of Yester was a prominent Scottish noble lineage associated with the Earls of Tweeddale and long-established estates in East Lothian.

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_69f76dcdc7708190a5f1751d53f40ffe completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcb14447048190ae67cc331783e9a0 completed May 7, 2026, 3:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a418546fd3c8190889b51c4ce4a0d15 completed June 28, 2026, 8:34 p.m.
NEDg Description generation batch_6a4185ef31d08190a98a0450b9b967a0 completed June 28, 2026, 8:37 p.m.
NED2 Entity disambiguation (via description) batch_6a41865e8b708190ae7dc8ea846a6899 completed June 28, 2026, 8:38 p.m.
Created at: May 3, 2026, 4:30 p.m.