Triple

T38588145
Position Surface form Disambiguated ID Type / Status
Subject Deeprun Tram to Stormwind City E932390 entity
Predicate hasAchievementRelated P9672 FINISHED
Object exploration achievements 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: exploration achievements | Statement: [Deeprun Tram to Stormwind City, hasAchievementRelated, exploration achievements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAchievementRelated
Context triple: [Deeprun Tram to Stormwind City, hasAchievementRelated, exploration achievements]
  • A. associatedAchievement chosen
    Indicates a relationship where one entity is linked to, or recognized in connection with, a particular achievement.
  • B. hasAchievements
    Indicates that an entity possesses or is associated with one or more notable accomplishments, awards, or completed goals.
  • C. hasRelatedTrophy
    Indicates that there exists a trophy that is associated with, linked to, or relevant to the given entity.
  • D. hasSubjectAchievement
    Indicates that an entity has achieved, accomplished, or earned a particular subject-related goal, milestone, or recognition.
  • E. hasAchievementType
    Indicates that an achievement is classified under a specific type or category of achievement.
  • 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_69fd5bf69acc819092a01e4259785dc3 completed May 8, 2026, 3:43 a.m.
PD Predicate disambiguation batch_69fd59b3f4ac8190a7f9dd3142da6e09 completed May 8, 2026, 3:34 a.m.
Created at: May 3, 2026, 4:32 p.m.