Triple
T38643557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Throne of the Four Winds |
E938661
|
entity |
| Predicate | concurrentTierRaids |
P191473
|
FINISHED |
| Object | Blackwing Descent |
—
|
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: Blackwing Descent | Statement: [Throne of the Four Winds, concurrentTierRaids, Blackwing Descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concurrentTierRaids Context triple: [Throne of the Four Winds, concurrentTierRaids, Blackwing Descent]
-
A.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
B.
raidsOccurEvery
Indicates that raids take place at regular intervals defined by a specific time period or frequency.
-
C.
mythicRaidSize
Indicates the number of participants involved when an activity or encounter is conducted at mythic difficulty.
-
D.
majorRaid
Indicates a large-scale, coordinated attack or incursion carried out against a target.
-
E.
raidingPattern
Indicates a recurring or characteristic way in which raids are planned, organized, or carried out between entities.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.