Triple
T20450314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buster Haywood |
E501631
|
entity |
| Predicate | hasLeagueRole |
P114265
|
FINISHED |
| Object | 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: player | Statement: [Buster Haywood, hasLeagueRole, player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeagueRole Context triple: [Buster Haywood, hasLeagueRole, player]
-
A.
hasFranchiseRole
Indicates that an entity holds a specific role or position within a franchise relationship.
-
B.
managedInLeague
Indicates that an entity served as a manager or head coach for a team participating in a specified league.
-
C.
memberOfSportsLeague
Indicates that an entity is formally part of, or participates as a member in, a specific sports league.
-
D.
hasGroupStageRole
Indicates that an entity holds a specific role or function within the group stage of a multi-stage process or event.
-
E.
leagueSystemRole
chosen
Indicates the specific role or function an entity holds within a league’s organizational or competitive system.
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68d0145d881908587b56c52aeea09 |
completed | April 20, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.