Triple
T4987527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maurice Podoloff Trophy |
E112039
|
entity |
| Predicate | teamOrIndividual |
P16455
|
FINISHED |
| Object | individual player |
—
|
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: individual player | Statement: [Maurice Podoloff Trophy, teamOrIndividual, individual player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamOrIndividual Context triple: [Maurice Podoloff Trophy, teamOrIndividual, individual player]
-
A.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
B.
typeOfTeams
Indicates the categories or kinds of teams to which an entity or group of entities belongs.
-
C.
isIndividualOrTeamAward
chosen
Indicates that an award is given either to a single individual or collectively to a team, rather than to another type of recipient.
-
D.
isTeamCompetition
Indicates that the competition involves participants organized into teams competing against each other rather than as individuals.
-
E.
professionalTeam
Indicates that one entity is a professional sports team associated with, representing, or employing the other entity.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.