Triple
T37539084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azuremyst Isle |
E933279
|
entity |
| Predicate | introducedWithRace |
P141977
|
FINISHED |
| Object | Draenei |
—
|
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: Draenei | Statement: [Azuremyst Isle, introducedWithRace, Draenei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedWithRace Context triple: [Azuremyst Isle, introducedWithRace, Draenei]
-
A.
introducesRace
chosen
Indicates that one entity presents, initiates, or brings into existence a race, competition, or racial category involving another entity.
-
B.
racedWith
Indicates that one entity participated in a race or competitive speed event together with another entity.
-
C.
initiallyRacedWith
Indicates that two entities participated in the same race or competitive event at the beginning of a relevant period or career.
-
D.
hasRace
Indicates that an entity possesses or is characterized by a particular race or racial classification.
-
E.
requiresRace
Indicates that one entity can only occur, be valid, or be accessed if a specified race or racial attribute condition is met.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:17 p.m.