Triple

T35013973
Position Surface form Disambiguated ID Type / Status
Subject Mundus E1010002 entity
Predicate metaphysicalCost P73251 FINISHED
Object sacrifice of Aedric power 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: sacrifice of Aedric power | Statement: [Mundus, metaphysicalCost, sacrifice of Aedric power]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: metaphysicalCost
Context triple: [Mundus, metaphysicalCost, sacrifice of Aedric power]
  • A. metaphysicalElement
    Indicates that one entity is a fundamental metaphysical component, aspect, or constituent of another entity or system.
  • B. hasMetaphysicalStructure
    Indicates that something possesses an underlying metaphysical organization or framework that defines its fundamental nature or mode of existence.
  • C. positionOnMetaphysics
    Indicates a relationship where an entity’s stance, view, or theoretical commitment regarding metaphysical questions or issues is specified.
  • D. hasCost chosen
    Indicates that one entity requires a specified amount of resources (such as money, time, or effort) to be obtained, used, or maintained by another entity.
  • E. increasedCostFor
    Indicates that one entity causes or experiences a rise in the cost associated with another entity or activity.
  • 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_69f76dcc3ac8819096a3ed52f5fa2523 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7858aa5508190a07dde993b3356fc completed May 3, 2026, 5:27 p.m.
PD Predicate disambiguation batch_69f7841812f081909d878955d114088e completed May 3, 2026, 5:21 p.m.
Created at: May 3, 2026, 4:01 p.m.