Triple
T36841953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenny Stills |
E910430
|
entity |
| Predicate | playedForTeamTo |
P59787
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Kenny Stills, playedForTeamTo, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedForTeamTo Context triple: [Kenny Stills, playedForTeamTo, 2014]
-
A.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
B.
teamPlayedFor
Indicates that a person was a member of and played for a particular sports team.
-
C.
playedForTeamEnd
chosen
Indicates that an entity’s period of playing for a particular team ended at a specified time or event.
-
D.
positionPlayedForTeam
Indicates the specific playing position or role an individual held while participating on a particular team.
-
E.
leagueOfTeamPlayedFor
Indicates the league or competition in which a given team, that an entity played for, participated.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:13 p.m.