Triple
T32422704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moonton |
E828497
|
entity |
| Predicate | offersInGameCosmeticsFor |
P119385
|
FINISHED |
| Object | Mobile Legends: Bang Bang |
—
|
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: Mobile Legends: Bang Bang | Statement: [Moonton, offersInGameCosmeticsFor, Mobile Legends: Bang Bang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersInGameCosmeticsFor Context triple: [Moonton, offersInGameCosmeticsFor, Mobile Legends: Bang Bang]
-
A.
hasCosmetics
Indicates that one entity possesses, uses, or is associated with cosmetic products or beauty-related items in relation to another entity or context.
-
B.
includesCosmetics
Indicates that one entity contains or encompasses cosmetic products or items as part of its contents or offerings.
-
C.
hasInGameItemType
chosen
Indicates that an entity possesses or is associated with a specific type or category of in-game item.
-
D.
offersGame
Indicates that one entity provides or makes a game available to another entity.
-
E.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 1, 2026, 12:54 a.m.