Triple

T9777821
Position Surface form Disambiguated ID Type / Status
Subject Narya E237289 entity
Predicate losesPowerWhen P9367 FINISHED
Object One Ring is destroyed 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: One Ring is destroyed | Statement: [Narya, losesPowerWhen, One Ring is destroyed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: losesPowerWhen
Context triple: [Narya, losesPowerWhen, One Ring is destroyed]
  • A. lostPowerIn
    Indicates that an entity has experienced a loss of electrical or functional power while in or at a specified location or context.
  • B. lostPower chosen
    Indicates that an entity has ceased to have electrical or functional power it previously possessed.
  • C. wasRemovedFromPowerBy
    Indicates that an entity lost its position of authority or control as a result of actions taken by another entity.
  • D. lostPowerDuring
    Indicates that an entity ceased to have electrical or functional power at some time during a specified event or interval.
  • E. hasNoPowerOver
    Indicates that one entity lacks authority, control, or influence over 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_69ca84d975a08190aab25b02a89bdab3 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda13545808190a47544b0cc666e20 completed April 1, 2026, 10:50 p.m.
PD Predicate disambiguation batch_69cd03d77c6c81909b675955bf113320 completed April 1, 2026, 11:39 a.m.
Created at: March 30, 2026, 8:26 p.m.