Triple

T14585344
Position Surface form Disambiguated ID Type / Status
Subject Syl Apps III E342299 entity
Predicate grandfather P979 FINISHED
Object Syl Apps E67950 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: Syl Apps | Statement: [Syl Apps III, grandfather, Syl Apps]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Syl Apps
Context triple: [Syl Apps III, grandfather, Syl Apps]
  • A. Syl Apps chosen
    Syl Apps was a Canadian professional ice hockey centre and Hall of Famer best known as a star player for the Toronto Maple Leafs in the 1930s and 1940s.
  • B. Syl Apps III
    Syl Apps III is a former Canadian professional ice hockey player and member of the prominent Apps hockey family.
  • C. Sly Apps
    Sly Apps was a Canadian Hall of Fame center renowned for his scoring prowess and two-way play with the Toronto Maple Leafs in the 1930s and 1940s.
  • D. Syl Apps Jr.
    Syl Apps Jr. is a former Canadian professional ice hockey centre who played in the NHL, notably for the Pittsburgh Penguins, during the 1970s.
  • E. Apps
    Apps is an English-language surname borne by various individuals, including figures such as Sylvanus Apps.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d822ddc0f081909cd8163c7de298cd completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb4209b988190ad2a7b2dead8ffed completed April 14, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdd5c79c488190a134d2b0435e899e completed May 8, 2026, 12:23 p.m.
Created at: April 10, 2026, 1:24 a.m.