Triple

T17319217
Position Surface form Disambiguated ID Type / Status
Subject Waipapa Power Station E420510 entity
Predicate hasInstalledCapacity P11312 FINISHED
Object 54 MW 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: 54 MW | Statement: [Waipapa Power Station, hasInstalledCapacity, 54 MW]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInstalledCapacity
Context triple: [Waipapa Power Station, hasInstalledCapacity, 54 MW]
  • A. installedCapacity chosen
    Indicates the maximum output or production capability that has been set up or built for a system, facility, or equipment, typically measured under specified conditions.
  • B. hasPlannedCapacity
    Indicates that an entity is associated with a specified capacity level that is planned or intended for future use rather than currently realized.
  • C. hasCapacityTo
    Indicates that one entity possesses the ability, power, or potential to perform an action or bring about a particular effect in relation to another entity or context.
  • D. hadCapacity
    Indicates that an entity possessed the ability, resources, or potential to perform a particular function or action.
  • E. hasCapacityType
    Indicates that an entity possesses a specific kind or classification of capacity or capability.
  • 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4399f84a881908dd99ecd7cc02708 completed April 19, 2026, 2:10 a.m.
PD Predicate disambiguation batch_69e3b01b9d1c8190a406dd941c9b11a1 completed April 18, 2026, 4:23 p.m.
Created at: April 10, 2026, 5:43 a.m.