Triple

T34595736
Position Surface form Disambiguated ID Type / Status
Subject 1973 NHL All-Star Game E888302 entity
Predicate linesman P32073 FINISHED
Object John D’Amico
John D’Amico was a longtime National Hockey League linesman renowned for his officiating career spanning several decades and numerous high-profile games.
E2288105 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: John D’Amico | Statement: [1973 NHL All-Star Game, linesman, John D’Amico]
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: John D’Amico
Triple: [1973 NHL All-Star Game, linesman, John D’Amico]
Generated description
John D’Amico was a longtime National Hockey League linesman renowned for his officiating career spanning several decades and numerous high-profile games.

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_69f349d3bfcc81909874c99e646fb3ea completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f721608bf08190a9698db00ff59f85 completed May 3, 2026, 10:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5a64511ca081909f7fa8ca57ae32f0 completed July 17, 2026, 5:20 p.m.
NEDg Description generation batch_6a5a650e016c8190ba6988a1555f1fc8 completed July 17, 2026, 5:23 p.m.
NED2 Entity disambiguation (via description) batch_6a5a65d62410819087d99143cb5288a8 completed July 17, 2026, 5:26 p.m.
Created at: May 1, 2026, 2:03 a.m.