Triple

T4468443
Position Surface form Disambiguated ID Type / Status
Subject CERN n_TOF facility E98435 entity
Predicate neutronProductionTarget P35502 FINISHED
Object lead target 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: lead target | Statement: [CERN n_TOF facility, neutronProductionTarget, lead target]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: neutronProductionTarget
Context triple: [CERN n_TOF facility, neutronProductionTarget, lead target]
  • A. neutronSpectrum
    Indicates the energy distribution or range of neutrons present in a given system, interaction, or environment.
  • B. neutronFluxType
    Indicates the specific classification or category of neutron flux characterizing how neutrons are distributed or behave in a given context.
  • C. usesNeutronReflector
    Indicates that an entity employs a neutron reflector to bounce escaping neutrons back into a region, typically to enhance or sustain a nuclear reaction.
  • D. neutrinoBeamDestination
    Indicates the target location or object toward which a neutrino beam is directed or intended to travel.
  • E. plannedTarget chosen
    Indicates that one entity has been designated or selected as the intended target or objective of another entity’s planned action or operation.
  • 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_69b3454b4ae481908967426dd37284d6 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b356fb69a0819099f0005779f4fcac completed March 13, 2026, 12:14 a.m.
PD Predicate disambiguation batch_69b3563bf4f8819081726cde3a34460b completed March 13, 2026, 12:11 a.m.
Created at: March 12, 2026, 11:34 p.m.