Triple
T38110634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galakrond, the Wretched |
E951643
|
entity |
| Predicate | hasCardBackPosition |
P190726
|
FINISHED |
| Object | Hero portrait replaces Warlock hero |
—
|
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: Hero portrait replaces Warlock hero | Statement: [Galakrond, the Wretched, hasCardBackPosition, Hero portrait replaces Warlock hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCardBackPosition Context triple: [Galakrond, the Wretched, hasCardBackPosition, Hero portrait replaces Warlock hero]
-
A.
hasCardBack
Indicates that an entity possesses or is associated with a specific card back design or reverse side.
-
B.
cardBackPosition
chosen
Indicates the spatial location or orientation of the back side of a card relative to a reference frame or other objects.
-
C.
cardPosition
Indicates the specific place or order a card occupies within a sequence, deck, or layout.
-
D.
cardBackInteraction
Indicates an interaction that occurs with or on the back side of a card, such as flipping, revealing, or otherwise engaging with that side.
-
E.
positionInCard
Indicates the relative placement or ordering of an element within a specific card.
- 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_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: May 3, 2026, 4:21 p.m.