Triple

T25136470
Position Surface form Disambiguated ID Type / Status
Subject Nashville Knights E629671 entity
Predicate notablePlayer P304 FINISHED
Object Mark Van Guilder
Mark Van Guilder is an American former professional ice hockey forward who briefly played in the NHL and spent much of his career in minor and European leagues.
E1676216 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: Mark Van Guilder | Statement: [Nashville Knights, notablePlayer, Mark Van Guilder]
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: Mark Van Guilder
Triple: [Nashville Knights, notablePlayer, Mark Van Guilder]
Generated description
Mark Van Guilder is an American former professional ice hockey forward who briefly played in the NHL and spent much of his career in minor and European leagues.

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_69e2ff338250819096ff6c8892804389 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f465ff8c1881909f42c293b0da9804 completed May 1, 2026, 8:36 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1075be9b388190b7099b139602f5cc completed May 22, 2026, 3:26 p.m.
NEDg Description generation batch_6a1076991b208190945d037fd9eef5f2 completed May 22, 2026, 3:30 p.m.
NED2 Entity disambiguation (via description) batch_6a1077bbf9448190bee4351dcb985c0c completed May 22, 2026, 3:35 p.m.
Created at: April 18, 2026, 6:29 a.m.