Triple

T38644190
Position Surface form Disambiguated ID Type / Status
Subject Vulpera E938673 entity
Predicate unlockRequiresQuest P192033 FINISHED
Object Allied Races: Vulpera 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: Allied Races: Vulpera | Statement: [Vulpera, unlockRequiresQuest, Allied Races: Vulpera]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: unlockRequiresQuest
Context triple: [Vulpera, unlockRequiresQuest, Allied Races: Vulpera]
  • A. questRequirementCount
    Indicates the number of required elements, tasks, or conditions that must be fulfilled for a quest.
  • B. isLegendaryQuest
    Indicates that a quest is of legendary status, typically denoting exceptional difficulty, rarity, or importance within its context.
  • C. unlockableIn
    Indicates that one entity can be unlocked, obtained, or made available within the context of another entity (such as a level, mode, or condition).
  • D. requiresSkill
    Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
  • E. hasQuestContentIn
    Indicates that a quest’s narrative or objectives are contained within or associated with a particular location, context, or container.
  • 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_69fcf1b3d9a08190850b388308656266 completed May 7, 2026, 8:10 p.m.
PD Predicate disambiguation batch_69fcf0226d8c8190b23dceafb1794995 completed May 7, 2026, 8:03 p.m.
PDg Predicate description generation batch_69fcf1b241888190a243f07051c71383 completed May 7, 2026, 8:10 p.m.
Created at: May 3, 2026, 4:32 p.m.