Triple

T26765401
Position Surface form Disambiguated ID Type / Status
Subject anti-Omega plus baryon E674923 entity
Predicate isSubjectToPauliExclusionPrinciple P65740 FINISHED
Object true 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: true | Statement: [anti-Omega plus baryon, isSubjectToPauliExclusionPrinciple, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isSubjectToPauliExclusionPrinciple
Context triple: [anti-Omega plus baryon, isSubjectToPauliExclusionPrinciple, true]
  • A. principalQuantumNumberCondition
    Indicates a constraint or requirement placed on the allowed values or range of a system’s principal quantum number in a given context.
  • B. hasProtonNumber
    Indicates that an entity (typically a chemical element or atom) possesses a specific number of protons in its nucleus.
  • C. fermionOrBoson chosen
    Indicates whether an entity is classified as a fermion or a boson according to its quantum statistical behavior.
  • D. hasElectronConfiguration
    Indicates that an entity (typically an atom or ion) possesses a specific arrangement of electrons in its atomic orbitals.
  • E. hasAtomicNumber
    Indicates that one entity is the chemical element whose atomic number (number of protons in its nucleus) is given by the other 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_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c663be481908f233d25d28713a4 completed May 2, 2026, 6:03 p.m.
Created at: April 27, 2026, 3:59 a.m.