Triple

T20417259
Position Surface form Disambiguated ID Type / Status
Subject Sectumsempra E500744 entity
Predicate castingRequirement P140062 FINISHED
Object wand movement 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: wand movement | Statement: [Sectumsempra, castingRequirement, wand movement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: castingRequirement
Context triple: [Sectumsempra, castingRequirement, wand movement]
  • A. typicalCasting
    Indicates that one entity is the usual or standard casting choice for portraying another entity (such as a role, character, or type).
  • B. castingReason
    Indicates the reason or justification for selecting or assigning a particular entity (e.g., a person or object) to a specific role, function, or category.
  • C. projectionRequirement
    Indicates a requirement that one entity be projected, mapped, or represented onto another according to specified criteria or constraints.
  • D. cast
    Indicates that an agent selects and assigns a person or thing to play a specific role or function in a production or context.
  • E. castingChoiceFor
    Indicates a relationship where a particular casting decision or option is selected or designated for a specific role, production, or performance.
  • 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_69e0b4a935588190b9446a99b37ced44 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67a44ecf48190ba5a3872af500dc8 completed April 20, 2026, 7:11 p.m.
PD Predicate disambiguation batch_69e5766df0008190a73c4f613c29678f completed April 20, 2026, 12:42 a.m.
PDg Predicate description generation batch_69e58d766b408190a1d3698145fb6d30 completed April 20, 2026, 2:20 a.m.
Created at: April 16, 2026, 11:30 a.m.