Triple
T38110601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galakrond, the Wretched |
E951643
|
entity |
| Predicate | hasCardClass |
P99617
|
FINISHED |
| Object | Warlock |
—
|
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: Warlock | Statement: [Galakrond, the Wretched, hasCardClass, Warlock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCardClass Context triple: [Galakrond, the Wretched, hasCardClass, Warlock]
-
A.
cardClass
chosen
Indicates the classification or category to which a given card belongs within a defined card system or schema.
-
B.
hasMatchCardType
Indicates that two or more items share the same card type or that an item is associated with a specific matching card type.
-
C.
hasCardinal
Indicates that something possesses or is associated with a specific cardinal number or quantity.
-
D.
containsCard
Indicates that one entity includes or holds a specific card as part of its contents or collection.
-
E.
hasClassSpecificCards
Indicates that certain cards are restricted to, or specifically associated with, a particular class or category.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0045a7b4c081908e4dedabda7cf790 |
completed | May 10, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_6a0042b148a48190974b173f352e4b7f |
completed | May 10, 2026, 8:32 a.m. |
Created at: May 3, 2026, 4:21 p.m.