Triple

T30392684
Position Surface form Disambiguated ID Type / Status
Subject CANDU reactor technology E773129 entity
Predicate regulatorInCanada P73569 FINISHED
Object Canadian Nuclear Safety Commission NE NERFINISHED

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: Canadian Nuclear Safety Commission | Statement: [CANDU reactor technology, regulatorInCanada, Canadian Nuclear Safety Commission]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatorInCanada
Context triple: [CANDU reactor technology, regulatorInCanada, Canadian Nuclear Safety Commission]
  • A. regulatorCountry
    Indicates the country that has regulatory authority or oversight over the referenced entity or activity.
  • B. regulatesProduct
    Indicates that one entity exercises control or governance over the production, distribution, or characteristics of a product belonging to or associated with another entity.
  • C. regulatorCovered chosen
    Indicates that an entity falls under the authority, oversight, or jurisdiction of a specified regulatory body.
  • D. regulatorType
    Indicates the specific kind or category of regulatory role or authority associated with an entity.
  • E. regulatedIn
    Indicates that one entity’s activity, expression, or occurrence is controlled, influenced, or modulated by another entity within a specific context or system.
  • 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_69f2248ef0a48190aa54d4d8ac3e5758 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fcab6e888881908ca9e18660928a40 completed May 7, 2026, 3:10 p.m.
PD Predicate disambiguation batch_69fc4562a5b88190bad48f083a6dcdfa completed May 7, 2026, 7:55 a.m.
Created at: April 29, 2026, 8:02 p.m.