Triple

T3644297
Position Surface form Disambiguated ID Type / Status
Subject MINOS experiment E77259 entity
Predicate hasNearDetectorFunction P49995 FINISHED
Object characterize the neutrino beam before oscillation 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: characterize the neutrino beam before oscillation | Statement: [MINOS experiment, hasNearDetectorFunction, characterize the neutrino beam before oscillation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearDetectorFunction
Context triple: [MINOS experiment, hasNearDetectorFunction, characterize the neutrino beam before oscillation]
  • A. hasNearbyFunction
    Indicates that one entity has another entity located close by that serves a related or supportive function.
  • B. hasNearbyMode
    Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
  • C. hasNearbyEventType
    Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
  • D. hasNearbyEvent
    Indicates that an event occurs close in space or time to the referenced entity.
  • E. hasNotableNearbyEntity
    Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
  • 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_69ad85de1b988190a45f8dbfebc806fc completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc35c28908190b253f4835918a2b4 completed March 8, 2026, 6:43 p.m.
PD Predicate disambiguation batch_69adb8445b2c8190ab07f6ad4e010d0e completed March 8, 2026, 5:56 p.m.
PDg Predicate description generation batch_69adb8e4ba948190a9b777cf7f788b96 completed March 8, 2026, 5:59 p.m.
Created at: March 8, 2026, 3:24 p.m.