Triple

T37458217
Position Surface form Disambiguated ID Type / Status
Subject The Thunder King E930851 entity
Predicate isPlayableInMode P69305 FINISHED
Object Arena
Arena is a competitive game mode in which players draft decks from random card selections to battle through a series of matches aiming for as many wins as possible before elimination.
E2228306 NE 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: Arena | Statement: [The Thunder King, isPlayableInMode, Arena]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Arena
Triple: [The Thunder King, isPlayableInMode, Arena]
Generated description
Arena is a competitive game mode in which players draft decks from random card selections to battle through a series of matches aiming for as many wins as possible before elimination.

Provenance (5 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_69fb8e336a24819098288895267cf472 completed May 6, 2026, 6:53 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40a7e37ac48190b560ad916d660551 completed June 28, 2026, 4:49 a.m.
NEDg Description generation batch_6a40a87e4c008190b9a9c54dd789dbc2 completed June 28, 2026, 4:52 a.m.
NED2 Entity disambiguation (via description) batch_6a40a901f21c8190ad963f201863a3b0 completed June 28, 2026, 4:54 a.m.
Created at: May 3, 2026, 4:17 p.m.