Triple

T34350533
Position Surface form Disambiguated ID Type / Status
Subject Lady Anne Erskine E881559 entity
Predicate spouseTitle P2097 FINISHED
Object 2nd Earl of Buccleuch
The 2nd Earl of Buccleuch was a Scottish nobleman from the influential Scott family, prominent in the Borders region during the early 17th century.
E2155206 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: 2nd Earl of Buccleuch | Statement: [Lady Anne Erskine, spouseTitle, 2nd Earl of Buccleuch]
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: 2nd Earl of Buccleuch
Triple: [Lady Anne Erskine, spouseTitle, 2nd Earl of Buccleuch]
Generated description
The 2nd Earl of Buccleuch was a Scottish nobleman from the influential Scott family, prominent in the Borders region during the early 17th century.

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_69f349bd06008190904c2f86c42749e3 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f713f29b3c819080d3b49623ec0f97 completed May 3, 2026, 9:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3885cfb5f081909da7685b5a1f42d0 completed June 22, 2026, 12:46 a.m.
NEDg Description generation batch_6a3889aab4208190aae74bda3f9845e1 completed June 22, 2026, 1:02 a.m.
NED2 Entity disambiguation (via description) batch_6a388a2a11848190ad9dfe71938b9771 completed June 22, 2026, 1:04 a.m.
Created at: May 1, 2026, 1:58 a.m.