Triple
T26765348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambda baryon |
E674922
|
entity |
| Predicate | hasPDGID |
P37463
|
FINISHED |
| Object | 3122 |
—
|
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: 3122 | Statement: [Lambda baryon, hasPDGID, 3122]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPDGID Context triple: [Lambda baryon, hasPDGID, 3122]
-
A.
PDGParticleID
chosen
Indicates that one entity is assigned a specific PDG (Particle Data Group) particle identification code, defining its particle type in high-energy physics.
-
B.
isGaugeBosonOf
Indicates that one particle serves as the gauge boson mediating the fundamental interaction associated with another entity (such as a force or symmetry group).
-
C.
hasProtonNumber
Indicates that an entity (typically a chemical element or atom) possesses a specific number of protons in its nucleus.
-
D.
hasGParity
Indicates that a particle possesses a specific value of G-parity, describing its behavior under the combined operation of charge conjugation and isospin rotation.
-
E.
hasParticleType
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
- 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_69f6192758648190ba2c0bfc9904994e |
completed | May 2, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:59 a.m.