Triple
T28828366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homestake solar neutrino experiment |
E727973
|
entity |
| Predicate | primaryNeutrinoSource |
P145650
|
FINISHED |
| Object | 8B solar neutrinos |
—
|
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: 8B solar neutrinos | Statement: [Homestake solar neutrino experiment, primaryNeutrinoSource, 8B solar neutrinos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryNeutrinoSource Context triple: [Homestake solar neutrino experiment, primaryNeutrinoSource, 8B solar neutrinos]
-
A.
detectedNeutrinoSource
chosen
Indicates that a particular source has been observed and identified as emitting detectable neutrinos.
-
B.
neutrinoSourceAbbreviation
Indicates that an entity is associated with a specific abbreviated designation used to identify a neutrino source.
-
C.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
D.
neutrinoFlavorAtSource
Indicates the specific neutrino flavor (e.g., electron, muon, tau) that a neutrino possesses at its point of origin or production.
-
E.
neutrinoProductionMethod
Indicates the process or mechanism by which neutrinos are generated or produced.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
Created at: April 28, 2026, 6:36 a.m.