Triple
T37465689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darkmoon Races Mini-Set |
E931027
|
entity |
| Predicate | mechanicsTheme |
P188661
|
FINISHED |
| Object | racing |
—
|
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: racing | Statement: [Darkmoon Races Mini-Set, mechanicsTheme, racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicsTheme Context triple: [Darkmoon Races Mini-Set, mechanicsTheme, racing]
-
A.
mechanicTheme
Indicates a relationship where an entity serves as the theme or primary object affected in a mechanical action or process.
-
B.
mechanics
Indicates that an entity is involved in the study, design, or application of forces and motion (i.e., mechanical principles) in relation to another entity or system.
-
C.
mechanicalThemeInHearthstone
chosen
Indicates that a particular mechanical or gameplay concept is used as a recurring thematic element within the game Hearthstone.
-
D.
mechanicalCategory
Indicates that one entity classifies or groups another entity according to its mechanical type, function, or mechanism-based category.
-
E.
featuresMechanic
Indicates that something includes or incorporates a particular mechanic as part of its design or functionality.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:17 p.m.