Triple
T37463493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter (Hearthstone class) |
E930976
|
entity |
| Predicate | hasSignatureTribe |
P196969
|
FINISHED |
| Object | Beast |
—
|
LITERAL 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: Beast | Statement: [Hunter (Hearthstone class), hasSignatureTribe, Beast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureTribe Context triple: [Hunter (Hearthstone class), hasSignatureTribe, Beast]
-
A.
hasTribalSeal
Indicates that an entity bears, is marked with, or is officially associated with a specific tribal seal.
-
B.
hasRecognizedTribe
Indicates that an entity is officially acknowledged or designated as a tribe by a relevant authority or governing body.
-
C.
recognizedTribeIncludes
Indicates that a formally recognized tribe encompasses or includes a particular subgroup, member, or entity within its official structure or membership.
-
D.
hasTribalRegister
Indicates that an entity is officially recorded or listed in a recognized tribal registry or roll.
-
E.
hasSignatureTrait
Indicates that an entity possesses a defining or characteristic trait that is especially distinctive or representative of it.
- F. None of above. chosen
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_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69fe6fe98e38819085100ce4c6cee5b8 |
completed | May 8, 2026, 11:21 p.m. |
Created at: May 3, 2026, 4:17 p.m.