Triple

T34345735
Position Surface form Disambiguated ID Type / Status
Subject James B. Speed E881426 entity
Predicate successor P78 FINISHED
Object Henry Stanbery
Henry Stanbery was an American lawyer and politician who served as U.S. Attorney General under President Andrew Johnson and played a key role in Johnson’s impeachment defense.
E2189640 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: Henry Stanbery | Statement: [James B. Speed, successor, Henry Stanbery]
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: Henry Stanbery
Triple: [James B. Speed, successor, Henry Stanbery]
Generated description
Henry Stanbery was an American lawyer and politician who served as U.S. Attorney General under President Andrew Johnson and played a key role in Johnson’s impeachment defense.

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_69f349bc55e881908c8e338ef76b0043 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f713ef2cb48190bf20608c3af3897d completed May 3, 2026, 9:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a39e6bc2cd08190aef7e2e35316a8e0 completed June 23, 2026, 1:51 a.m.
NEDg Description generation batch_6a39eb96fa2081909dc4790068e70df1 completed June 23, 2026, 2:12 a.m.
NED2 Entity disambiguation (via description) batch_6a39ef75b4108190a21eae0fd8d705e8 completed June 23, 2026, 2:29 a.m.
Created at: May 1, 2026, 1:58 a.m.