Triple

T32897307
Position Surface form Disambiguated ID Type / Status
Subject John Scott, 1st Earl of Eldon E841510 entity
Predicate nobleTitle P914 FINISHED
Object Earl of Eldon
The Earl of Eldon is a British peerage title most famously associated with John Scott, a prominent 18th–19th century lawyer and Lord Chancellor of Great Britain.
E2107859 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: Earl of Eldon | Statement: [John Scott, 1st Earl of Eldon, nobleTitle, Earl of Eldon]
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: Earl of Eldon
Triple: [John Scott, 1st Earl of Eldon, nobleTitle, Earl of Eldon]
Generated description
The Earl of Eldon is a British peerage title most famously associated with John Scott, a prominent 18th–19th century lawyer and Lord Chancellor of Great Britain.

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_69f34945ae408190b72d8118c83beb77 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d074751c8190ac5bce9d70c9c5c8 completed May 3, 2026, 4:35 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3752cba0948190b67d4415356bb783 completed June 21, 2026, 2:56 a.m.
NEDg Description generation batch_6a3753394308819095e3f8c080869717 completed June 21, 2026, 2:58 a.m.
NED2 Entity disambiguation (via description) batch_6a3753c33f708190adafff500ed06ca8 completed June 21, 2026, 3 a.m.
Created at: May 1, 2026, 1:18 a.m.