Triple
T32422709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moonton |
E828497
|
entity |
| Predicate | hasCasualModeIn |
P198291
|
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, hasCasualModeIn, Mobile Legends: Bang Bang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCasualModeIn Context triple: [Moonton, hasCasualModeIn, Mobile Legends: Bang Bang]
-
A.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
B.
availableInMode
Indicates that something can be used, accessed, or functions within a specified mode or operational setting.
-
C.
hasModeOfAction
Indicates that one entity (typically a treatment, drug, or intervention) exerts its effect through a specified mechanism or biological process.
-
D.
hasCasino
Indicates that an entity includes, contains, or is associated with a casino facility or gambling establishment.
-
E.
hasCoopMode
Indicates that something supports or includes a cooperative mode of operation or gameplay involving multiple participants working together.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
| PDg | Predicate description generation | batch_69fed83a3b8c819092a3bd1ca9d9b38b |
completed | May 9, 2026, 6:46 a.m. |
Created at: May 1, 2026, 12:54 a.m.