Triple

T1096109
Position Surface form Disambiguated ID Type / Status
Subject Z boson E24274 entity
Predicate hasChargeConjugationParity P5367 FINISHED
Object +1 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: +1 | Statement: [Z boson, hasChargeConjugationParity, +1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasChargeConjugationParity
Context triple: [Z boson, hasChargeConjugationParity, +1]
  • A. hasChargeConjugation
    Indicates that one entity is the charge-conjugated counterpart (particle vs. antiparticle form) of another entity.
  • B. hasParity
    Indicates that two entities share the same parity property (e.g., both even or both odd) with respect to a specified attribute or value.
  • C. chargeConjugationEigenstate chosen
    Indicates that a particle or state is an eigenstate of the charge conjugation operator, meaning it transforms into itself up to a definite eigenvalue under charge conjugation.
  • D. isOwnAntiparticle
    Indicates that an entity is identical to its own antiparticle, meaning it serves simultaneously as both particle and antiparticle in that relationship.
  • E. hasWeakIsospin
    Indicates that an entity possesses a specified value of weak isospin, representing its charge under the weak nuclear interaction.
  • 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_69a4940542308190ac2a0b1f730b7cfc completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b99ffb3481908cd168b6c58e1c6d completed March 1, 2026, 10:11 p.m.
PD Predicate disambiguation batch_69a4b7448c148190a3c9a4158ebd05b4 completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.