Triple
T37457721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadowreaper Anduin |
E930839
|
entity |
| Predicate | synergyCard |
P170824
|
FINISHED |
| Object | Raza the Chained |
—
|
NE NERFINISHED |
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: Raza the Chained | Statement: [Shadowreaper Anduin, synergyCard, Raza the Chained]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: synergyCard Context triple: [Shadowreaper Anduin, synergyCard, Raza the Chained]
-
A.
raceSynergy
Indicates how the combination of different races or species enhances, modifies, or interacts to affect overall effectiveness or outcome.
-
B.
cardCompatibility
chosen
Indicates how well two or more cards work together in terms of synergy, effectiveness, or intended combined use.
-
C.
Omen Gaming Hub
Indicates a software platform that manages, optimizes, or enhances gaming-related activities or settings for users.
-
D.
platformMate
Indicates that two entities are located on the same platform or share the same platform context at a given time.
-
E.
actsSynergisticallyWith
Indicates that two entities interact in a way that enhances or amplifies each other's effects or outcomes beyond what they would achieve independently.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.