Triple

T6087997
Position Surface form Disambiguated ID Type / Status
Subject OPERA E135686 entity
Predicate reportedObservationOfNuTauAppearance P68580 FINISHED
Object 2015 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: 2015 | Statement: [OPERA, reportedObservationOfNuTauAppearance, 2015]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reportedObservationOfNuTauAppearance
Context triple: [OPERA, reportedObservationOfNuTauAppearance, 2015]
  • A. neutrinoDetectionSignificance
    Indicates the statistical strength or confidence level that a detected signal is due to neutrinos rather than background noise or random fluctuations.
  • B. neutrinoBurstDetected
    Indicates that a sudden, significant increase in neutrino emissions has been observed or recorded.
  • C. neutrinoBeamDestination
    Indicates the target location or object toward which a neutrino beam is directed or intended to travel.
  • D. measuredNumberOfLightNeutrinoFamilies
    Indicates the experimentally determined count of distinct light neutrino families inferred from measurements.
  • E. hasObservedAsymmetry
    Indicates that one entity has detected or recorded an imbalance, difference, or non-uniformity in another entity or in a relationship between entities.
  • F. None of above. chosen

Provenance (4 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_69c0087bcc788190b20f093d3a6c60ec completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c057a6f7588190b265d6005fbaf6b3 completed March 22, 2026, 8:57 p.m.
PD Predicate disambiguation batch_69c049f3b1ec8190bea67a7bec6442a5 completed March 22, 2026, 7:58 p.m.
PDg Predicate description generation batch_69c04e8d4a148190bd8f95caae978e1b completed March 22, 2026, 8:18 p.m.
Created at: March 22, 2026, 4:12 p.m.