Triple
T38463780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangzhou Charge |
E912513
|
entity |
| Predicate | hasEsportsDivision |
P46164
|
FINISHED |
| Object | Overwatch |
—
|
NE NERFINISHED |
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: Overwatch | Statement: [Guangzhou Charge, hasEsportsDivision, Overwatch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEsportsDivision Context triple: [Guangzhou Charge, hasEsportsDivision, Overwatch]
-
A.
isEsportsDivisionOf
chosen
Indicates that one organization functions as the esports division or competitive gaming branch of another, typically larger, parent organization.
-
B.
hasESportsLeague
Indicates that an entity organizes, sponsors, or is otherwise associated with a specific esports league.
-
C.
hadEsportsProgram
Indicates that an institution or organization operated an esports program during a specified time period.
-
D.
hasEsportsTitle
Indicates that an entity possesses or has been awarded a specific esports-related title or championship.
-
E.
isOfficialEsportsTeamOf
Indicates that a team is formally recognized or designated as the official esports representative of a particular organization, brand, or 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.