Triple
T37871905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imaginators |
E944627
|
entity |
| Predicate | hasBattleClass |
P131706
|
FINISHED |
| Object | Brawler |
—
|
LITERAL 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: Brawler | Statement: [Imaginators, hasBattleClass, Brawler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattleClass Context triple: [Imaginators, hasBattleClass, Brawler]
-
A.
hasKeyBattle
Indicates that an entity is associated with a major or decisive battle that is central to its history, role, or significance.
-
B.
hasChampionClass
chosen
Indicates that an entity is associated with, or belongs to, a particular champion class or category.
-
C.
hasBattlePassIntegration
Indicates that an entity is functionally connected to or supports features of a battle pass system.
-
D.
hasBattleFormat
Indicates that an entity is associated with, or conducted under, a particular battle or combat ruleset or format.
-
E.
hasCombatType
Indicates that an entity is associated with a particular mode or category of combat it uses or participates in.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 3, 2026, 4:19 p.m.