Triple

T13043922
Position Surface form Disambiguated ID Type / Status
Subject Indianapolis Racers E327267 entity
Predicate jerseyNumberWornByWayneGretzky P104927 FINISHED
Object 14 LITERAL 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: 14 | Statement: [Indianapolis Racers, jerseyNumberWornByWayneGretzky, 14]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: jerseyNumberWornByWayneGretzky
Context triple: [Indianapolis Racers, jerseyNumberWornByWayneGretzky, 14]
  • A. jerseyNumber
    Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
  • B. hasJerseyNumberRetired
    Indicates that an entity has had its jersey number officially retired, typically in recognition of its contributions or achievements.
  • C. jerseyNumberRetiredInHisHonor
    Indicates that a person’s jersey number has been officially retired by a team or organization as a tribute to that person’s contributions or legacy.
  • D. jerseyNumberTeam chosen
    Indicates the association between a specific jersey number and the team for which that jersey number is used or assigned.
  • E. wearsJerseyFor
    Indicates that one entity wears a jersey representing, belonging to, or in support of another entity (such as a team, organization, or individual).
  • F. None of above.

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_69d8076e64308190904fb5c93517c901 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d98a9829b48190b23624b6b3df4600 completed April 10, 2026, 11:41 p.m.
PD Predicate disambiguation batch_69d9803aca4c8190b1015cd159cc47a9 completed April 10, 2026, 10:56 p.m.
Created at: April 9, 2026, 8:56 p.m.