Triple
T32422708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moonton |
E828497
|
entity |
| Predicate | hasRankedModeIn |
P189460
|
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, hasRankedModeIn, Mobile Legends: Bang Bang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankedModeIn Context triple: [Moonton, hasRankedModeIn, Mobile Legends: Bang Bang]
-
A.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
B.
hasRanks
Indicates that one entity possesses, is assigned, or is associated with one or more rank levels or hierarchical positions.
-
C.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
D.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
E.
hasRankedPerson
Indicates that an entity has assigned or holds a person in a specific rank or ordered position relative to others.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 1, 2026, 12:54 a.m.