Triple

T30810515
Position Surface form Disambiguated ID Type / Status
Subject Earl of Erroll E784630 entity
Predicate hasTitleNumbering P7922 FINISHED
Object 42nd Earl of Erroll
The 42nd Earl of Erroll is the current holder of a historic Scottish peerage long associated with the hereditary office of Lord High Constable of Scotland.
E2143082 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: 42nd Earl of Erroll | Statement: [Earl of Erroll, hasTitleNumbering, 42nd Earl of Erroll]
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: 42nd Earl of Erroll
Triple: [Earl of Erroll, hasTitleNumbering, 42nd Earl of Erroll]
Generated description
The 42nd Earl of Erroll is the current holder of a historic Scottish peerage long associated with the hereditary office of Lord High Constable of Scotland.

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_69f224b4eda48190bd212ce4f3901e56 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69063edbc81909e7735954aabee0b completed May 3, 2026, 12:01 a.m.
NED1 Entity disambiguation (via context triple) batch_6a38400ea668819096080fabd29f67e0 completed June 21, 2026, 7:48 p.m.
NEDg Description generation batch_6a3840c3a9008190adfe194ce03be34d completed June 21, 2026, 7:51 p.m.
NED2 Entity disambiguation (via description) batch_6a3844a277c48190b9bbb145e14f3a49 completed June 21, 2026, 8:08 p.m.
Created at: April 29, 2026, 8:43 p.m.