Triple
T37516087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shalamayne |
E932636
|
entity |
| Predicate | primaryWielderTitle |
P205948
|
FINISHED |
| Object | King of Stormwind |
E932175
|
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: King of Stormwind | Statement: [Shalamayne, primaryWielderTitle, King of Stormwind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWielderTitle Context triple: [Shalamayne, primaryWielderTitle, King of Stormwind]
-
A.
wielderRole
Indicates the specific role or function an entity has in relation to the item or power it wields.
-
B.
formerWielder
Indicates that one entity previously wielded, controlled, or used another entity, but no longer does so.
-
C.
primaryUserTitle
Indicates the main professional or role-based title associated with a user in a given context.
-
D.
laterWielder
Indicates that one entity becomes the wielder or user of an object or power after another entity who wielded it earlier.
-
E.
primaryWearer
Indicates that one entity is the main or principal user or wearer of another entity (such as an item or garment).
- F. None of above. chosen
Provenance (5 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40a7e7cd348190b5d5648af2fd21cc |
completed | June 28, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.