Triple
T37463069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Mosh |
E930965
|
entity |
| Predicate | isLegendaryForSet |
P189402
|
FINISHED |
| Object | Journey to Un'Goro |
—
|
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: Journey to Un'Goro | Statement: [King Mosh, isLegendaryForSet, Journey to Un'Goro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLegendaryForSet Context triple: [King Mosh, isLegendaryForSet, Journey to Un'Goro]
-
A.
isLegendaryStatus
Indicates that an entity possesses a legendary status, typically signifying exceptional rarity, renown, or significance within a given context.
-
B.
partOfHeroicEquipmentSetOf
Indicates that an item is a component belonging to a specific heroic equipment set.
-
C.
isLegendaryMinionForClass
Indicates that a minion is a legendary card specifically associated with a given class.
-
D.
includesLegendaryCard
Indicates that an entity (such as a deck, pack, or collection) contains at least one legendary card.
-
E.
hasLegendaryPokémon
Indicates that an entity (such as a location, trainer, or group) possesses, contains, or is associated with at least one Legendary Pokémon.
- 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_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:17 p.m.