Triple

T26765397
Position Surface form Disambiguated ID Type / Status
Subject anti-Omega plus baryon E674923 entity
Predicate hasCorrespondingParticle P6587 FINISHED
Object Omega minus baryon NE NERFINISHED

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: Omega minus baryon | Statement: [anti-Omega plus baryon, hasCorrespondingParticle, Omega minus baryon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCorrespondingParticle
Context triple: [anti-Omega plus baryon, hasCorrespondingParticle, Omega minus baryon]
  • A. associatedWithParticle
    Indicates that an entity has a contextual or functional connection to a specific particle (such as a subatomic particle or grammatical particle).
  • B. hasParticleType
    Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
  • C. hasSmallerCounterpart
    Indicates that one entity has another entity as its corresponding version that is smaller in size, scale, or magnitude.
  • D. hasCounterpart chosen
    Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
  • E. hasCorrespondenceForm
    Indicates that there exists a specific format, template, or structural representation used for the correspondence associated with an entity.
  • 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_69eecda85298819097ee1c38a3d772e7 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69fe610e1f6881908f10070ba64643cf completed May 8, 2026, 10:17 p.m.
PD Predicate disambiguation batch_69fe604c6c008190ad659e9b9fa82f7b completed May 8, 2026, 10:14 p.m.
Created at: April 27, 2026, 3:59 a.m.