Triple
T24003677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King |
E594313
|
entity |
| Predicate | playsRoleInEsports |
P100150
|
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: [King, playsRoleInEsports, player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsRoleInEsports Context triple: [King, playsRoleInEsports, player]
-
A.
isOfficialEsportsTeamOf
Indicates that a team is formally recognized or designated as the official esports representative of a particular organization, brand, or entity.
-
B.
isEsportsDivisionOf
Indicates that one organization functions as the esports division or competitive gaming branch of another, typically larger, parent organization.
-
C.
ownsEsportsFranchise
Indicates that one entity has ownership or controlling stake in an esports franchise associated with another entity.
-
D.
hasESportsLeague
Indicates that an entity organizes, sponsors, or is otherwise associated with a specific esports league.
-
E.
esportsStatus
chosen
Indicates the competitive or professional esports standing or role associated with an 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d467108481909e33de1c7319738a |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.