Triple

T37096627
Position Surface form Disambiguated ID Type / Status
Subject Hexen: Deathkings of the Dark Citadel E918579 entity
Predicate supportsCharacterClass P32439 FINISHED
Object fighter — 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: fighter | Statement: [Hexen: Deathkings of the Dark Citadel, supportsCharacterClass, fighter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsCharacterClass
Context triple: [Hexen: Deathkings of the Dark Citadel, supportsCharacterClass, fighter]
  • A. hasCharacterClass
    Indicates that an entity (such as a character) belongs to or is assigned a particular character class or role type.
  • B. supportsClassification
    Indicates that one entity provides the capability or functionality needed for another entity to perform or maintain a specific classification.
  • C. capturesCharacter
    Indicates that one entity seizes, traps, or takes control of another character.
  • D. containsCompatibilityCharacters
    Indicates that one entity includes or is associated with characters that are designated as compatibility characters relative to another encoding or standard.
  • E. supportedClass chosen
    Indicates that one entity is a class or type that is recognized, handled, or operable within the capabilities or context provided by another entity.
  • 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_69f76e9a48bc8190a3947508d8bca408 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a037c8e2c648190a65fc9c7872861af completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a11efc08190bb7cacc1325b4dc6 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:14 p.m.