Triple

T37459696
Position Surface form Disambiguated ID Type / Status
Subject Tinkmaster Overspark (reprint-related theme) E930886 entity
Predicate characterRace P200062 FINISHED
Object Gnome 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: Gnome | Statement: [Tinkmaster Overspark (reprint-related theme), characterRace, Gnome]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: characterRace
Context triple: [Tinkmaster Overspark (reprint-related theme), characterRace, Gnome]
  • A. usedByCharacterRace
    Indicates that something (such as an item, ability, or feature) is utilized or employed by a particular character race.
  • B. raceInLegendarium
    Indicates that an entity belongs to a particular fictional race or species within a specific mythological or fantasy legendarium.
  • C. playableRace
    Indicates that an entity is a race or species that players are allowed to choose and control in a game or interactive system.
  • D. fictionalRace chosen
    Indicates that one entity is a fictional or imaginary race or species to which the other entity belongs or is associated.
  • E. cardRace
    Indicates that one entity participates in or is associated with a competitive race involving cards or card-based vehicles relative to 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_69f76ec1a1148190b0a961f188d621b0 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fff328ddc0819080642334a41fcf95 completed May 10, 2026, 2:53 a.m.
PD Predicate disambiguation batch_69fff2e0971c819081aa66f4a6a34b28 completed May 10, 2026, 2:52 a.m.
Created at: May 3, 2026, 4:17 p.m.