Triple
T26562406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyrese Maxey |
E666285
|
entity |
| Predicate | playsForOrganizationType |
P146139
|
FINISHED |
| Object | professional sports team |
—
|
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: professional sports team | Statement: [Tyrese Maxey, playsForOrganizationType, professional sports team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsForOrganizationType Context triple: [Tyrese Maxey, playsForOrganizationType, professional sports team]
-
A.
teamTypePlayedFor
chosen
Indicates the type or category of team (e.g., national, club, youth) that an entity has played for.
-
B.
typeOfSportOrganizationManaged
Indicates the specific kind of sports organization that an entity is responsible for managing.
-
C.
memberOfSportsOrganization
Indicates that an entity belongs to or is affiliated with a specific sports organization or club.
-
D.
playsForTitle
Indicates that an entity performs or competes on behalf of a team, organization, or group under a specific title or designation.
-
E.
leagueOrganization
Indicates that an organization is responsible for running, governing, or officially managing a sports league or competitive league.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 1:53 a.m.