Triple
T11544301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mage (Hearthstone class) |
E273743
|
entity |
| Predicate | classIdentity |
P14829
|
FINISHED |
| Object | Spell-focused gameplay |
—
|
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: Spell-focused gameplay | Statement: [Mage (Hearthstone class), classIdentity, Spell-focused gameplay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classIdentity Context triple: [Mage (Hearthstone class), classIdentity, Spell-focused gameplay]
-
A.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
-
B.
identityConcept
chosen
Indicates that two concepts are the same in identity, representing exactly the same underlying idea or meaning.
-
C.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
D.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
E.
identityBasis
Indicates that one entity serves as the defining basis, criterion, or foundation for determining the identity of 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.