Triple
T10376186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | electron neutrino |
E244513
|
entity |
| Predicate | hasLeptonFlavor |
P5363
|
FINISHED |
| Object | electron lepton number |
—
|
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: electron lepton number | Statement: [electron neutrino, hasLeptonFlavor, electron lepton number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeptonFlavor Context triple: [electron neutrino, hasLeptonFlavor, electron lepton number]
-
A.
hasBranchingRatioToLeptons
Indicates the proportion of a particle’s decays that result in leptons among all its possible decay channels.
-
B.
leptonNumber
chosen
Indicates that a specified lepton number value is assigned to or conserved by a given particle or interaction in a physical process.
-
C.
hasQuarkFlavors
Indicates that an entity (such as a particle) possesses specific types (flavors) of quarks as its constituents.
-
D.
hasBranchingRatioToHadrons
Indicates the fraction of a particle’s decays that result in hadronic final states (i.e., decays into hadrons).
-
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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98278e08190a4d3ff88b4039e49 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:02 p.m.