Triple
T36945878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Overwatch League season |
E913908
|
entity |
| Predicate | hasInternationalTeams |
P202899
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2019 Overwatch League season, hasInternationalTeams, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternationalTeams Context triple: [2019 Overwatch League season, hasInternationalTeams, true]
-
A.
hasInternationalTeam
Indicates that an entity is associated with or possesses a team that operates or competes at the international level.
-
B.
isInternationalCompetition
Indicates that a competition involves participants or teams from multiple countries or spans more than one nation’s jurisdiction.
-
C.
isLinkedToInternationalCompetitions
Indicates that there is an association or connection between the entity and one or more international competitions.
-
D.
isLeadingInternationalTeam
Indicates that one entity is currently in charge of directing and managing a team composed of members from multiple countries.
-
E.
internationalTeam
Indicates that a team is composed of members from multiple countries or operates across national boundaries.
- F. None of above. chosen
Provenance (4 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00ccadb6908190ab810a7c05315fa8 |
completed | May 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_6a00cc0f86b88190a0d2c43618558f86 |
completed | May 10, 2026, 6:18 p.m. |
| PDg | Predicate description generation | batch_6a00ccabfe8c8190be7c2bafe2323c2b |
completed | May 10, 2026, 6:21 p.m. |
Created at: May 3, 2026, 4:13 p.m.