Triple
T37509847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helm of Domination |
E932187
|
entity |
| Predicate | firstBearerInLore |
P115337
|
FINISHED |
| Object | Ner’zhul |
E1035792
|
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: Ner’zhul | Statement: [Helm of Domination, firstBearerInLore, Ner’zhul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBearerInLore Context triple: [Helm of Domination, firstBearerInLore, Ner’zhul]
-
A.
firstBearer
Indicates that the subject is the earliest or original entity to hold, possess, or carry the specified role, title, attribute, or item.
-
B.
firstHolderInCanon
chosen
Indicates that the subject is the earliest entity, in the canonical timeline or storyline, known to have held or possessed the specified object, title, or role.
-
C.
saidToBeTheFirst
Indicates that one entity is claimed or regarded as being the earliest or original instance of something relative to others.
-
D.
firstEncounteredBy
Indicates that one entity is the person or agent who initially discovered, met, or came across the other entity for the first time.
-
E.
firstKnownLord
Indicates that the subject is the earliest historically or canonically recorded lord associated with the object.
- 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_69f76ec5268481909ea01c73aeeefd42 |
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_6a412c948b088190a0f1055f92990947 |
completed | June 28, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.