Triple
T38644480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rise of Azshara |
E938680
|
entity |
| Predicate | introducesRaid |
P99612
|
FINISHED |
| Object | The Eternal Palace |
—
|
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: The Eternal Palace | Statement: [Rise of Azshara, introducesRaid, The Eternal Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesRaid Context triple: [Rise of Azshara, introducesRaid, The Eternal Palace]
-
A.
introducedRaid
chosen
Indicates that one entity initiated or brought about a raid involving another entity or target.
-
B.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
C.
addsRaid
Indicates that an entity initiates or includes a raid event or operation involving another entity.
-
D.
hasRaid
Indicates that an entity is associated with, participates in, or is the target of a raid event or operation.
-
E.
introducesRace
Indicates that one entity presents, initiates, or brings into existence a race, competition, or racial category involving another entity.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 3, 2026, 4:32 p.m.