Triple

T38589995
Position Surface form Disambiguated ID Type / Status
Subject Ashkandi, Greatsword of the Brotherhood E932430 entity
Predicate canBeSocketed P200914 FINISHED
Object false (in original classic) 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: false (in original classic) | Statement: [Ashkandi, Greatsword of the Brotherhood, canBeSocketed, false (in original classic)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeSocketed
Context triple: [Ashkandi, Greatsword of the Brotherhood, canBeSocketed, false (in original classic)]
  • A. canBeEnchantedWith
    Indicates that an entity is capable of receiving or being affected by a specified enchantment.
  • B. mayBeWorn
    Indicates that one entity is suitable or allowed to be worn by another entity, typically as clothing, accessories, or adornment.
  • C. hasSoulGemAbility
    Indicates that an entity possesses the capability to use, interact with, or be affected by a soul gem and its associated powers or functions.
  • D. oftenEquippedWith
    Indicates that one type of entity is frequently or typically outfitted, furnished, or supplied with another entity.
  • E. hasJewel
    Indicates that one entity possesses, contains, or is adorned with a jewel in relation to another entity.
  • 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_69f76ec654d48190b421111cf26e54d9 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ffb82be8148190a1c870d467a28c80 completed May 9, 2026, 10:41 p.m.
PD Predicate disambiguation batch_69ffb7bbd550819094052e9a0d0ae320 completed May 9, 2026, 10:39 p.m.
PDg Predicate description generation batch_69ffb82b40788190bf401344a3f288dd completed May 9, 2026, 10:41 p.m.
Created at: May 3, 2026, 4:32 p.m.