Triple

T38024458
Position Surface form Disambiguated ID Type / Status
Subject C. William O’Neill E948729 entity
Predicate spouse P13 FINISHED
Object Betty Hewson O’Neill
Betty Hewson O’Neill was the wife of C. William O’Neill, a prominent Ohio politician who served as governor and chief justice of the Ohio Supreme Court.
E2283169 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: Betty Hewson O’Neill | Statement: [C. William O’Neill, spouse, Betty Hewson O’Neill]
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: Betty Hewson O’Neill
Triple: [C. William O’Neill, spouse, Betty Hewson O’Neill]
Generated description
Betty Hewson O’Neill was the wife of C. William O’Neill, a prominent Ohio politician who served as governor and chief justice of the Ohio Supreme Court.

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_69f76efd1bc48190a729097fe5177b61 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbc97398d481909afc0b73753c4c7f completed May 6, 2026, 11:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a42458f9b488190bcb5eda521b43707 completed June 29, 2026, 10:14 a.m.
NEDg Description generation batch_6a424663f1c481909dc832d8484c6447 completed June 29, 2026, 10:18 a.m.
NED2 Entity disambiguation (via description) batch_6a4246b4a8208190bdf87ace5e912e82 completed June 29, 2026, 10:19 a.m.
Created at: May 3, 2026, 4:20 p.m.