Triple
T37457029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elementals (Hearthstone) |
E930824
|
entity |
| Predicate | hasNotableCard |
P50468
|
FINISHED |
| Object | Ragnaros the Firelord |
E975370
|
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: Ragnaros the Firelord | Statement: [Elementals (Hearthstone), hasNotableCard, Ragnaros the Firelord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCard Context triple: [Elementals (Hearthstone), hasNotableCard, Ragnaros the Firelord]
-
A.
hasNotableCardFamily
Indicates that an entity is associated with a specific, distinguished group or family of related cards.
-
B.
hasNotableItem
chosen
Indicates that an entity possesses, contains, or is associated with an item considered notable or significant in some context.
-
C.
hasNotableCredit
Indicates that an entity is recognized for having a significant or noteworthy contribution, role, or acknowledgment associated with it.
-
D.
hasNotabilityFor
Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
-
E.
hasNotableRecord
Indicates that an entity possesses a distinguished or noteworthy achievement, performance, or documented accomplishment in some domain.
- 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_6a408267ad1c819094e50a10578dace9 |
completed | June 28, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.