Triple

T37100384
Position Surface form Disambiguated ID Type / Status
Subject Earl of Home E918685 entity
Predicate hasTitle P38 FINISHED
Object Lord Dunglass
Lord Dunglass is a courtesy title traditionally used by the heir apparent to the Earl of Home in the Scottish peerage.
E2214815 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: Lord Dunglass | Statement: [Earl of Home, hasTitle, Lord Dunglass]
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: Lord Dunglass
Triple: [Earl of Home, hasTitle, Lord Dunglass]
Generated description
Lord Dunglass is a courtesy title traditionally used by the heir apparent to the Earl of Home in the Scottish peerage.

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_69f76e9a48bc8190a3947508d8bca408 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb2fee46548190b60e864c81d6787b completed May 6, 2026, 12:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3f6a0f27c88190b76c9110544e47f2 completed June 27, 2026, 6:13 a.m.
NEDg Description generation batch_6a3f6c091a548190809a8a3b4f142e83 completed June 27, 2026, 6:22 a.m.
NED2 Entity disambiguation (via description) batch_6a3ffa5151a8819081fd0b81ff6d3749 completed June 27, 2026, 4:29 p.m.
Created at: May 3, 2026, 4:14 p.m.