Triple
T37463941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrior |
E930986
|
entity |
| Predicate | heroClassOf |
P100346
|
FINISHED |
| Object | Garrosh Hellscream (Hearthstone) |
—
|
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: Garrosh Hellscream (Hearthstone) | Statement: [Warrior, heroClassOf, Garrosh Hellscream (Hearthstone)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroClassOf Context triple: [Warrior, heroClassOf, Garrosh Hellscream (Hearthstone)]
-
A.
heroClass
chosen
Indicates the character class or role that a hero belongs to within a given system or context.
-
B.
heroDepicted
Indicates that one entity is portrayed or represented as a hero in relation to another entity.
-
C.
heroClassRestriction
Indicates that a particular action, item, or ability is restricted to heroes of specific classes or class types.
-
D.
heroPower
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
E.
heroPowerName
Indicates the specific power or ability associated with a hero.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.