Triple

T29900093
Position Surface form Disambiguated ID Type / Status
Subject Paradox Engine E759385 entity
Predicate convertedManaCost P175360 FINISHED
Object 5 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: 5 | Statement: [Paradox Engine, convertedManaCost, 5]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: convertedManaCost
Context triple: [Paradox Engine, convertedManaCost, 5]
  • A. hasManaCost
    Indicates that an entity (such as a spell or ability) requires a specified amount of mana to be used or activated.
  • B. usesMinimumCopiesPerCard
    Indicates that there is a constraint specifying the minimum number of copies of each card that must be used or included in a given context.
  • C. damageCostNote
    Indicates a descriptive note or explanation associated with the cost of damage, providing contextual or clarifying information about that damage-related expense.
  • D. conversionPoints
    Indicates a relationship where one entity defines specific points, stages, or conditions at which another entity is converted, transformed, or counted as a conversion.
  • E. reducedCostOf
    Indicates that one entity represents a lowered or discounted cost associated with another entity, typically compared to a standard or original price.
  • 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_69f2245f1cf88190978c70d1a1d2cb73 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f6d1d916f881909575c2b22c416a5b completed May 3, 2026, 4:40 a.m.
PD Predicate disambiguation batch_69f6cfe2183481908ae4e85a59c66f69 completed May 3, 2026, 4:32 a.m.
PDg Predicate description generation batch_69f6d0d331dc8190be5aa6bfc6365e67 completed May 3, 2026, 4:36 a.m.
Created at: April 29, 2026, 6:06 p.m.