Triple

T6010127
Position Surface form Disambiguated ID Type / Status
Subject T2K E133809 entity
Predicate reportedEvidenceFor P3650 FINISHED
Object leptonic CP violation (delta_CP near -pi/2) 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: leptonic CP violation (delta_CP near -pi/2) | Statement: [T2K, reportedEvidenceFor, leptonic CP violation (delta_CP near -pi/2)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reportedEvidenceFor
Context triple: [T2K, reportedEvidenceFor, leptonic CP violation (delta_CP near -pi/2)]
  • A. providesEvidenceFor chosen
    Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
  • B. usedEvidenceType
    Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
  • C. hasNoEvidenceOf
    Indicates that there is no supporting proof, data, or documentation confirming the existence or occurrence of the referenced condition, event, or relationship.
  • D. believedProvidedBy
    Indicates that something is thought or assumed to have been supplied or made available by a particular source or provider.
  • E. reportedOn
    Indicates that one entity has provided an account, description, or coverage of another entity, typically as news, documentation, or an official report.
  • 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_69c0087361a48190905c6b55969852b8 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04f4ffa008190a8ef701b82260219 completed March 22, 2026, 8:21 p.m.
PD Predicate disambiguation batch_69c049e4daf4819099bf870dc700e0a2 completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:06 p.m.