Triple
T11544278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard format (Hearthstone) |
E273742
|
entity |
| Predicate | metagameChangesWith |
P92084
|
FINISHED |
| Object | new expansion releases |
—
|
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: new expansion releases | Statement: [Standard format (Hearthstone), metagameChangesWith, new expansion releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metagameChangesWith Context triple: [Standard format (Hearthstone), metagameChangesWith, new expansion releases]
-
A.
notableRuleChange
Indicates a significant modification to an established rule or set of rules that meaningfully alters how they apply or are enforced.
-
B.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
C.
changesWith
chosen
Indicates that one entity varies or is modified in response to changes in another entity.
-
D.
decorChanges
Indicates that an entity alters or updates the decorative appearance or arrangement of another entity or environment.
-
E.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e1d754819089f3b6be3404fa0b |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.