Triple
T37462046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yogg-Saron Spell Mage |
E930941
|
entity |
| Predicate | primaryCard |
P55012
|
FINISHED |
| Object | Yogg-Saron, Hope's End |
E930914
|
NE 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: Yogg-Saron, Hope's End | Statement: [Yogg-Saron Spell Mage, primaryCard, Yogg-Saron, Hope's End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCard Context triple: [Yogg-Saron Spell Mage, primaryCard, Yogg-Saron, Hope's End]
-
A.
primaryAccountIn
Indicates that an entity serves as the main or default account within a specified context, group, or container.
-
B.
primaryFor
chosen
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
C.
primaryCharge
Indicates that one charge is designated as the main or most significant charge associated with an entity or case, typically among multiple possible charges.
-
D.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
E.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
- F. None of above.
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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409527a5b481908e0fc1923b46f406 |
completed | June 28, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.