Triple

T37459712
Position Surface form Disambiguated ID Type / Status
Subject Tinkmaster Overspark (reprint-related theme) E930886 entity
Predicate hasSameRulesTextAs P6249 FINISHED
Object original Tinkmaster Overspark (at time of reprint) 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: original Tinkmaster Overspark (at time of reprint) | Statement: [Tinkmaster Overspark (reprint-related theme), hasSameRulesTextAs, original Tinkmaster Overspark (at time of reprint)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSameRulesTextAs
Context triple: [Tinkmaster Overspark (reprint-related theme), hasSameRulesTextAs, original Tinkmaster Overspark (at time of reprint)]
  • A. hasRule
    Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
  • B. usesRulesFrom chosen
    Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
  • C. hasNumberOfRules
    Indicates the specific count of rules associated with or applicable to an entity.
  • D. hasRuleOver
    Indicates that one entity holds authority, control, or governance over another entity.
  • E. hasRuleFor
    Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
  • 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_69fcec5f8b448190b48330a19b462d24 completed May 7, 2026, 7:47 p.m.
PD Predicate disambiguation batch_69fceaf1e23881908ca24160a638e329 completed May 7, 2026, 7:41 p.m.
Created at: May 3, 2026, 4:17 p.m.