Triple

T28501738
Position Surface form Disambiguated ID Type / Status
Subject Popham E721251 entity
Predicate hasNotableBearer P458 FINISHED
Object Alexander Popham
Alexander Popham was a 17th-century English politician who served as a Member of Parliament and was involved in the parliamentary cause during the English Civil War.
E1827031 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: Alexander Popham | Statement: [Popham, hasNotableBearer, Alexander Popham]
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: Alexander Popham
Triple: [Popham, hasNotableBearer, Alexander Popham]
Generated description
Alexander Popham was a 17th-century English politician who served as a Member of Parliament and was involved in the parliamentary cause during the English Civil War.

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_69f01a5afdac8190ac6e72d5c100bd58 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f64f43700c8190b16ba41e7a6b4809 completed May 2, 2026, 7:23 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cc363e9a48190ab7657c9d2bfe7f2 completed May 31, 2026, 11:25 p.m.
NEDg Description generation batch_6a1cc3ede124819081809a5cbbc5a3d6 completed May 31, 2026, 11:27 p.m.
NED2 Entity disambiguation (via description) batch_6a1cc4b69e5c8190bae7beb6a8b82aa7 completed May 31, 2026, 11:31 p.m.
Created at: April 28, 2026, 3:07 a.m.