Triple
T37460750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kel'Thuzad (card) |
E930909
|
entity |
| Predicate | legendaryRule |
P187923
|
FINISHED |
| Object | Only one copy per deck |
—
|
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: Only one copy per deck | Statement: [Kel'Thuzad (card), legendaryRule, Only one copy per deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legendaryRule Context triple: [Kel'Thuzad (card), legendaryRule, Only one copy per deck]
-
A.
legendaryPeriod
Indicates a time span associated with legends or mythic events rather than strictly historical chronology.
-
B.
ruleOfImmortals
Indicates a governing or authoritative relationship exercised by immortal beings over others.
-
C.
knownAsLegend
Indicates that an entity is widely regarded or celebrated as a legend.
-
D.
famousLegend
Indicates that the subject is widely known and celebrated in stories, myths, or folklore, often with enduring cultural significance.
-
E.
legendaryNameFor
Indicates that one entity is known or referred to by the other entity as its legendary or mythic name.
- F. None of above. chosen
Provenance (4 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_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.