Triple

T35035346
Position Surface form Disambiguated ID Type / Status
Subject Michael J. Dillon U.S. Courthouse E1010894 entity
Predicate namedAfter P63 FINISHED
Object Michael J. Dillon
Michael J. Dillon was a prominent public figure in Buffalo, New York, whose service and legacy led to a federal courthouse being named in his honor.
E2192457 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: Michael J. Dillon | Statement: [Michael J. Dillon U.S. Courthouse, namedAfter, Michael J. Dillon]
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: Michael J. Dillon
Triple: [Michael J. Dillon U.S. Courthouse, namedAfter, Michael J. Dillon]
Generated description
Michael J. Dillon was a prominent public figure in Buffalo, New York, whose service and legacy led to a federal courthouse being named in his honor.

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_69f76dcea02c81908542a223f6d5059f completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7854bd63881909c02160150ed3ce3 completed May 3, 2026, 5:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3a093ad3b48190b686da5a36a2cefe completed June 23, 2026, 4:19 a.m.
NEDg Description generation batch_6a3a0eb2a24481909d8b4a73cbf40397 completed June 23, 2026, 4:42 a.m.
NED2 Entity disambiguation (via description) batch_6a3a111d998c81909bb013a68874f244 completed June 23, 2026, 4:52 a.m.
Created at: May 3, 2026, 4:01 p.m.