Triple
T9056642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last to Die |
E217015
|
entity |
| Predicate | hasCardBack |
P86131
|
FINISHED |
| Object | Magic: The Gathering standard card back |
—
|
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: Magic: The Gathering standard card back | Statement: [Last to Die, hasCardBack, Magic: The Gathering standard card back]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCardBack Context triple: [Last to Die, hasCardBack, Magic: The Gathering standard card back]
-
A.
hasNumberOfCards
Indicates that an entity is associated with a specific quantity of cards.
-
B.
isThroughDeck
Indicates that one object passes completely through another object or surface, extending from one side to the other.
-
C.
frontDesignSameAsBack
Indicates that the design on the front side of an object is identical to the design on its back side.
-
D.
cardSize
Indicates the specific dimensions or format assigned to a card within a given context or system.
-
E.
cardFormat
Indicates the specific layout or structural style in which a card or card-like item is presented or encoded.
- 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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7a75d8e881909414d745ec054182 |
completed | April 1, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee6d83c819095d8ed0779aa8511 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:10 p.m.