Triple
T32422694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moonton |
E828497
|
entity |
| Predicate | supportsEsportsLeaguesFor |
P143738
|
FINISHED |
| Object | Mobile Legends: Bang Bang |
E2010500
|
NE 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: Mobile Legends: Bang Bang | Statement: [Moonton, supportsEsportsLeaguesFor, Mobile Legends: Bang Bang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEsportsLeaguesFor Context triple: [Moonton, supportsEsportsLeaguesFor, Mobile Legends: Bang Bang]
-
A.
esportSupportedBy
Indicates that an esports activity, event, or organization is backed, sponsored, or otherwise provided with resources or assistance by a supporting entity.
-
B.
esportsSupportStatus
Indicates whether and how an entity provides support, resources, or recognition for esports activities or organizations.
-
C.
hasESportsLeague
Indicates that an entity organizes, sponsors, or is otherwise associated with a specific esports league.
-
D.
supportedLeague
chosen
Indicates that an entity has provided backing, endorsement, or assistance to a particular league.
-
E.
supportsLeagueType
Indicates that one entity is compatible with, or designed to work with, a particular type or category of league.
- F. None of above.
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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a349e9ddc088190bcd1046507318ca7 |
completed | June 19, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:54 a.m.