Triple

T26856772
Position Surface form Disambiguated ID Type / Status
Subject John Egerton, 1st Earl of Bridgewater E676217 entity
Predicate givenName P17 FINISHED
Object John
John Egerton, 1st Earl of Bridgewater, was a 17th-century English nobleman and politician who served as Lord President of the Council of Wales and the Marches.
E1743114 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: John | Statement: [John Egerton, 1st Earl of Bridgewater, givenName, John]
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: John
Triple: [John Egerton, 1st Earl of Bridgewater, givenName, John]
Generated description
John Egerton, 1st Earl of Bridgewater, was a 17th-century English nobleman and politician who served as Lord President of the Council of Wales and the Marches.

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_69eee9b9d7708190a15d7485709ae981 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61b96bcc08190b8d9cb07cf19876a completed May 2, 2026, 3:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12131bc53c81908660a605bd832f27 completed May 23, 2026, 8:50 p.m.
NEDg Description generation batch_6a12143774a0819094274f9c58871f16 completed May 23, 2026, 8:55 p.m.
NED2 Entity disambiguation (via description) batch_6a1214e92af48190b857bf935b0fd49d completed May 23, 2026, 8:58 p.m.
Created at: April 27, 2026, 5:22 a.m.