Triple

T21787978
Position Surface form Disambiguated ID Type / Status
Subject Sudbury Neutrino Observatory E537889 entity
Predicate shieldingPurpose P64472 FINISHED
Object reduction of cosmic-ray background 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: reduction of cosmic-ray background | Statement: [Sudbury Neutrino Observatory, shieldingPurpose, reduction of cosmic-ray background]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shieldingPurpose
Context triple: [Sudbury Neutrino Observatory, shieldingPurpose, reduction of cosmic-ray background]
  • A. hasProtectionPurpose chosen
    Indicates that something is intended or designed to serve a protective function or goal.
  • B. requiresShielding
    Indicates that one entity must be protected or insulated from another entity or from certain conditions, typically for safety or proper functioning.
  • C. shieldType
    Indicates the specific kind or category of shield associated with an entity or interaction.
  • D. shieldDescribedAs
    Indicates that a shield is characterized or portrayed using a particular description or set of attributes.
  • E. providesProtectionIn
    Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, 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_69e0c47198f881908cb0d237266c10e9 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0621c68588190977891055e80a499 completed April 28, 2026, 7:30 a.m.
PD Predicate disambiguation batch_69e6be751ce881909badced245ef76c7 completed April 21, 2026, 12:01 a.m.
Created at: April 16, 2026, 6:52 p.m.