Triple
T37599725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvermoon City |
E935489
|
entity |
| Predicate | playableRacesHub |
P192259
|
FINISHED |
| Object | blood elf starting hub |
—
|
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: blood elf starting hub | Statement: [Silvermoon City, playableRacesHub, blood elf starting hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableRacesHub Context triple: [Silvermoon City, playableRacesHub, blood elf starting hub]
-
A.
playableRace
Indicates that an entity is a race or species that players are allowed to choose and control in a game or interactive system.
-
B.
playableRaceForClass
Indicates that a particular race is allowed or eligible to be chosen as a playable option for a given character class.
-
C.
playableClasses
Indicates that the referenced entity can be used or selected as a character class that a player is allowed to play.
-
D.
raceInGame
Indicates that an entity participates as a race or faction within a particular game.
-
E.
cardRace
Indicates that one entity participates in or is associated with a competitive race involving cards or card-based vehicles relative to another entity.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 3, 2026, 4:18 p.m.