Triple
T37459771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plague Quarter |
E930888
|
entity |
| Predicate | hasMechanicTheme |
P188661
|
FINISHED |
| Object | deathrattle |
—
|
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: deathrattle | Statement: [Plague Quarter, hasMechanicTheme, deathrattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMechanicTheme Context triple: [Plague Quarter, hasMechanicTheme, deathrattle]
-
A.
mechanicTheme
Indicates a relationship where an entity serves as the theme or primary object affected in a mechanical action or process.
-
B.
hasMechanicalFeature
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
C.
mechanicalThemeInHearthstone
chosen
Indicates that a particular mechanical or gameplay concept is used as a recurring thematic element within the game Hearthstone.
-
D.
featuresMechanic
Indicates that something includes or incorporates a particular mechanic as part of its design or functionality.
-
E.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: May 3, 2026, 4:17 p.m.