Triple
T37463062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Mosh |
E930965
|
entity |
| Predicate | isLegendaryMinionForClass |
P189035
|
FINISHED |
| Object | Warrior |
—
|
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: Warrior | Statement: [King Mosh, isLegendaryMinionForClass, Warrior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLegendaryMinionForClass Context triple: [King Mosh, isLegendaryMinionForClass, Warrior]
-
A.
isLegendaryStatus
Indicates that an entity possesses a legendary status, typically signifying exceptional rarity, renown, or significance within a given context.
-
B.
includesLegendaryForEachClass
Indicates that the set or collection contains at least one legendary instance or element corresponding to each distinct class represented.
-
C.
isMythicPrototypeOf
Indicates that one entity serves as the mythic or legendary archetype, model, or original form upon which the other entity is based or derived.
-
D.
isMythical
Indicates that the entity is considered mythical, existing only in legend, folklore, or imagination rather than in reality.
-
E.
hasChampionClass
Indicates that an entity is associated with, or belongs to, a particular champion class or category.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.