Triple
T37893378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deathbringer Saurfang |
E945208
|
entity |
| Predicate | raidEncounterIn |
P188713
|
FINISHED |
| Object | Icecrown Citadel |
—
|
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: Icecrown Citadel | Statement: [Deathbringer Saurfang, raidEncounterIn, Icecrown Citadel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidEncounterIn Context triple: [Deathbringer Saurfang, raidEncounterIn, Icecrown Citadel]
-
A.
raidBossIn
chosen
Indicates that an entity serves as or is designated as the raid boss within a specified raid, instance, or location.
-
B.
raidingPattern
Indicates a recurring or characteristic way in which raids are planned, organized, or carried out between entities.
-
C.
finalRaidEncounter
Indicates that an encounter represents the ultimate or concluding boss fight or challenge within a raid.
-
D.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
E.
raidConductedBy
Indicates that a particular raid was carried out or executed by a specified agent or organization.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.