Triple
T37460439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapphiron |
E930902
|
entity |
| Predicate | positionInRaid |
P200440
|
FINISHED |
| Object | penultimate boss of Naxxramas |
—
|
LITERAL FINISHED |
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: penultimate boss of Naxxramas | Statement: [Sapphiron, positionInRaid, penultimate boss of Naxxramas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRaid Context triple: [Sapphiron, positionInRaid, penultimate boss of Naxxramas]
-
A.
positionInMission
chosen
Indicates the specific role, rank, or placement an entity holds within a particular mission or operation.
-
B.
positionInBattle
Indicates the specific role or placement an entity occupies within the formation or structure of a battle.
-
C.
positionInSector
Indicates the specific location or placement of an entity within a defined sector or sub-area.
-
D.
positionOnTerritory
Indicates that one entity occupies or is located at a specific position within the spatial extent of another entity’s territory.
-
E.
raidEntranceLocation
Indicates the location where a raid begins or where raiders enter a target area.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:17 p.m.