Triple
T37516083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shalamayne |
E932636
|
entity |
| Predicate | famousWielder |
P40163
|
FINISHED |
| Object | Varian Wrynn |
—
|
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: Varian Wrynn | Statement: [Shalamayne, famousWielder, Varian Wrynn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousWielder Context triple: [Shalamayne, famousWielder, Varian Wrynn]
-
A.
lastKnownWielder
Indicates the entity that was most recently known to possess or wield another entity.
-
B.
hasNotableWeaponNamedAfter
Indicates that an entity possesses a notable weapon that is named after another specific entity.
-
C.
laterWielder
Indicates that one entity becomes the wielder or user of an object or power after another entity who wielded it earlier.
-
D.
mostFamousBearer
chosen
Indicates that one entity is the most widely recognized or renowned individual associated with a particular name, title, or attribute compared to all other bearers of it.
-
E.
famousLegend
Indicates that the subject is widely known and celebrated in stories, myths, or folklore, often with enduring cultural significance.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
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.