Triple
T38585022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magisters' Terrace |
E932326
|
entity |
| Predicate | connectedToRaid |
P183436
|
FINISHED |
| Object | Sunwell Plateau |
—
|
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: Sunwell Plateau | Statement: [Magisters' Terrace, connectedToRaid, Sunwell Plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToRaid Context triple: [Magisters' Terrace, connectedToRaid, Sunwell Plateau]
-
A.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
B.
hasRaid
Indicates that an entity is associated with, participates in, or is the target of a raid event or operation.
-
C.
addsRaid
chosen
Indicates that an entity initiates or includes a raid event or operation involving another entity.
-
D.
raidID
Indicates a unique identifier that associates entities with a specific raid event or operation.
-
E.
raidedRegion
Indicates that an agent carried out a raid targeting or occurring within a specified region.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:32 p.m.