Triple

T31750349
Position Surface form Disambiguated ID Type / Status
Subject Pease River E810397 entity
Predicate namedAfter P63 FINISHED
Object Elisha M. Pease
Elisha M. Pease was a 19th-century American politician who served multiple terms as governor of Texas and played a key role in the state's early legal and financial development.
E1988218 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: Elisha M. Pease | Statement: [Pease River, namedAfter, Elisha M. Pease]
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: Elisha M. Pease
Triple: [Pease River, namedAfter, Elisha M. Pease]
Generated description
Elisha M. Pease was a 19th-century American politician who served multiple terms as governor of Texas and played a key role in the state's early legal and financial development.

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_69f348e233cc819083b6695f70cd75d8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6ab5262c88190bc54527b57ec2a81 completed May 3, 2026, 1:56 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2ed4cca0c081909a19a19a7e65cc02 completed June 14, 2026, 4:20 p.m.
NEDg Description generation batch_6a2ed5d5e50481909643301cbb095e03 completed June 14, 2026, 4:24 p.m.
NED2 Entity disambiguation (via description) batch_6a2ed721fb788190ba3719843972260f completed June 14, 2026, 4:30 p.m.
Created at: April 30, 2026, 11:27 p.m.