Triple
T11544566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaman (Hearthstone class) |
E273748
|
entity |
| Predicate | cardBackAssociation |
P86131
|
FINISHED |
| Object | Shaman-specific card backs |
—
|
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: Shaman-specific card backs | Statement: [Shaman (Hearthstone class), cardBackAssociation, Shaman-specific card backs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardBackAssociation Context triple: [Shaman (Hearthstone class), cardBackAssociation, Shaman-specific card backs]
-
A.
cardGameAssociatedWith
Indicates that there is a relationship of association between a card game and another entity, such as a person, place, event, or concept.
-
B.
hasCardBack
chosen
Indicates that an entity possesses or is associated with a specific card back design or reverse side.
-
C.
shipAssociatedWith
Indicates that there is a relevant connection or involvement between a ship and another entity, such as ownership, operation, registration, or functional association.
-
D.
cardType
Indicates the classification or category assigned to a card within a given system or context.
-
E.
keyAssociation
Indicates an associative relationship where one entity serves as a key used to identify, access, or link to another entity or set of entities.
- 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.