Triple

T29346356
Position Surface form Disambiguated ID Type / Status
Subject Paladin E744182 entity
Predicate typicalAccessory P130667 FINISHED
Object shield 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: shield | Statement: [Paladin, typicalAccessory, shield]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalAccessory
Context triple: [Paladin, typicalAccessory, shield]
  • A. accessory
    Indicates that one entity serves as a supplementary or supporting item to another, often enhancing its function, use, or appearance.
  • B. typicalWear
    Indicates that one entity is commonly or characteristically worn by the other in typical situations or contexts.
  • C. typicalGear chosen
    Indicates that the object represents the usual or standard equipment or gear commonly associated with the subject.
  • D. typicalJewellery
    Indicates that the object is a kind of jewellery that is commonly or characteristically associated with the given entity.
  • E. typicalItem
    Indicates that an item is a representative or characteristic example of a broader category, class, or set.
  • 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_69f0a79a2d748190bc30abd469298b37 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_6a01a534a8908190aa888d6be5deb824 completed May 11, 2026, 9:45 a.m.
PD Predicate disambiguation batch_6a01a507c1f081909ff6abc5575db0bb completed May 11, 2026, 9:44 a.m.
Created at: April 28, 2026, 2:02 p.m.