Triple
T37463488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter (Hearthstone class) |
E930976
|
entity |
| Predicate | hasBasicHero |
P100004
|
FINISHED |
| Object | Rexxar |
—
|
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: Rexxar | Statement: [Hunter (Hearthstone class), hasBasicHero, Rexxar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasicHero Context triple: [Hunter (Hearthstone class), hasBasicHero, Rexxar]
-
A.
baseHero
chosen
Indicates that one entity serves as the primary or foundational hero associated with another entity.
-
B.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
C.
hasPrimaryCharacter
Indicates that an entity features another entity as its main or central character.
-
D.
hasHeroicResponder
Indicates that an entity is associated with or supported by another entity that performs a heroic or emergency response action on its behalf.
-
E.
hasBaseHP
Indicates that an entity possesses a specified amount of base hit points (HP) as its fundamental health value.
- 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_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.