Triple
T37472268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halls of Atonement |
E931181
|
entity |
| Predicate | hasAchievementCategory |
P74191
|
FINISHED |
| Object | Dungeons & Raids |
—
|
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: Dungeons & Raids | Statement: [Halls of Atonement, hasAchievementCategory, Dungeons & Raids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAchievementCategory Context triple: [Halls of Atonement, hasAchievementCategory, Dungeons & Raids]
-
A.
hasAchievementType
chosen
Indicates that an achievement is classified under a specific type or category of achievement.
-
B.
hasAchievements
Indicates that an entity possesses or is associated with one or more notable accomplishments, awards, or completed goals.
-
C.
hasSubjectAchievement
Indicates that an entity has achieved, accomplished, or earned a particular subject-related goal, milestone, or recognition.
-
D.
hasMissionCategory
Indicates that an entity is associated with a specific type or category of mission.
-
E.
hasAwardCategoryWithin
Indicates that an award belongs to or is classified under a specific award category within a broader award system or hierarchy.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:17 p.m.