Triple
T11544418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogue (Hearthstone class) |
E273745
|
entity |
| Predicate | coreStrength |
P6664
|
FINISHED |
| Object | single-target removal |
—
|
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: single-target removal | Statement: [Rogue (Hearthstone class), coreStrength, single-target removal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreStrength Context triple: [Rogue (Hearthstone class), coreStrength, single-target removal]
-
A.
strengthType
Indicates the specific category or nature of strength associated with an entity or relationship (e.g., physical, structural, or conceptual strength).
-
B.
strengthPeak
Indicates the point or period at which an entity’s strength reaches its maximum level.
-
C.
strength
chosen
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
D.
strengthDescription
Indicates a description or characterization of the degree of strength associated with an entity or relationship.
-
E.
strengthSource
Indicates that one entity serves as the origin or provider of strength, power, or resilience for another entity.
- 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.