Triple
T26765396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | anti-Omega plus baryon |
E674923
|
entity |
| Predicate | isMatterOrAntimatter |
P161208
|
FINISHED |
| Object | antimatter |
—
|
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: antimatter | Statement: [anti-Omega plus baryon, isMatterOrAntimatter, antimatter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMatterOrAntimatter Context triple: [anti-Omega plus baryon, isMatterOrAntimatter, antimatter]
-
A.
isOwnAntiparticle
Indicates that an entity is identical to its own antiparticle, meaning it serves simultaneously as both particle and antiparticle in that relationship.
-
B.
antiparticleType
Indicates that one particle is the corresponding antiparticle type of another particle.
-
C.
hasAntiquark
Indicates that one particle is associated with, or contains, a corresponding antiquark as part of its composition or structure.
-
D.
isBoson
Indicates that the subject is a boson, i.e., a particle that follows Bose–Einstein statistics and typically mediates forces or can occupy the same quantum state as others.
-
E.
fermionOrBoson
Indicates whether an entity is classified as a fermion or a boson according to its quantum statistical behavior.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6192758648190ba2c0bfc9904994e |
completed | May 2, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:59 a.m.