Triple
T34616314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DONUT |
E888874
|
entity |
| Predicate | studiesLeptonFamily |
P179705
|
FINISHED |
| Object | tau lepton family |
—
|
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: tau lepton family | Statement: [DONUT, studiesLeptonFamily, tau lepton family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiesLeptonFamily Context triple: [DONUT, studiesLeptonFamily, tau lepton family]
-
A.
leptonNumber
Indicates that a specified lepton number value is assigned to or conserved by a given particle or interaction in a physical process.
-
B.
measuredNumberOfLightNeutrinoFamilies
Indicates the experimentally determined count of distinct light neutrino families inferred from measurements.
-
C.
hasBranchingRatioToLeptons
Indicates the proportion of a particle’s decays that result in leptons among all its possible decay channels.
-
D.
typicalFermionMass
Indicates the characteristic or representative mass value associated with a given type of fermion.
-
E.
quarkModel
Indicates that one entity represents or employs a quark-based theoretical model to describe the internal structure or behavior of another entity (such as a particle or system).
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:03 a.m.