Triple
T26765601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ξ*− (dss) |
E674927
|
entity |
| Predicate | hasNetLeptonNumber |
P5363
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Ξ*− (dss), hasNetLeptonNumber, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetLeptonNumber Context triple: [Ξ*− (dss), hasNetLeptonNumber, 0]
-
A.
leptonNumber
chosen
Indicates that a specified lepton number value is assigned to or conserved by a given particle or interaction in a physical process.
-
B.
hasBranchingRatioToLeptons
Indicates the proportion of a particle’s decays that result in leptons among all its possible decay channels.
-
C.
hasBaryonNumber
Indicates that an entity possesses a specific baryon number, quantifying its net content of baryonic matter (baryons minus antibaryons).
-
D.
hasFermionNumber
Indicates that an entity is associated with a specific fermion number value, representing its net count of fermionic particles (fermions minus antifermions).
-
E.
measuredNumberOfLightNeutrinoFamilies
Indicates the experimentally determined count of distinct light neutrino families inferred from measurements.
- 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_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 27, 2026, 3:59 a.m.