Triple
T32422707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moonton |
E828497
|
entity |
| Predicate | hasHeroSystemIn |
P127054
|
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, hasHeroSystemIn, Mobile Legends: Bang Bang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroSystemIn Context triple: [Moonton, hasHeroSystemIn, Mobile Legends: Bang Bang]
-
A.
hasMagicSystemElement
Indicates that an entity’s magic system includes or is characterized by a specific elemental component or aspect.
-
B.
hasGameSystem
chosen
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
-
C.
hasHeroicResponder
Indicates that an entity is associated with or supported by another entity that performs a heroic or emergency response action on its behalf.
-
D.
isHeroicVariantAvailable
Indicates whether a special or enhanced "heroic" version of something is currently obtainable or enabled.
-
E.
partOfHeroicEquipmentSetOf
Indicates that an item is a component belonging to a specific heroic equipment set.
- 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_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 1, 2026, 12:54 a.m.