Triple
T37465742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Gryphon |
E931028
|
entity |
| Predicate | cardPoolChange |
P100024
|
FINISHED |
| Object | older expansions rotated to Wild at its start |
—
|
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: older expansions rotated to Wild at its start | Statement: [Year of the Gryphon, cardPoolChange, older expansions rotated to Wild at its start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardPoolChange Context triple: [Year of the Gryphon, cardPoolChange, older expansions rotated to Wild at its start]
-
A.
cardSetRotation
chosen
Indicates a relationship where a card set is rotated in or out of an active pool or format, typically marking its transition into or out of current use.
-
B.
cardVariant
Indicates that one card is a specific version or variation of another base card.
-
C.
bondChange
Indicates a change in the type, order, or presence of a bond between two entities, such as forming, breaking, or altering a connection.
-
D.
cardPosition
Indicates the specific place or order a card occupies within a sequence, deck, or layout.
-
E.
cardColor
Indicates the color attribute assigned to a card in the relationship.
- 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_69f76ec2af148190897d101070d7f415 |
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. |
Created at: May 3, 2026, 4:17 p.m.