Triple
T28828368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homestake solar neutrino experiment |
E727973
|
entity |
| Predicate | energyThreshold |
P14326
|
FINISHED |
| Object | about 0.814 MeV |
—
|
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: about 0.814 MeV | Statement: [Homestake solar neutrino experiment, energyThreshold, about 0.814 MeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyThreshold Context triple: [Homestake solar neutrino experiment, energyThreshold, about 0.814 MeV]
-
A.
thresholdFor
chosen
Indicates that one entity specifies the minimum or limiting value at which a condition, effect, or state involving another entity begins to occur or change.
-
B.
thresholdMet
Indicates that a specified limit or condition has been reached or exceeded.
-
C.
energyLevel
Indicates the amount or intensity of energy possessed, produced, or exhibited by an entity in a given state or context.
-
D.
elevationThreshold
Indicates a specified elevation level at which a condition, effect, or change in state becomes applicable or is triggered.
-
E.
energyLevelModel
Indicates a relationship where an entity’s energy level is represented, quantified, or characterized according to a specific model or modeling framework.
- 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_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 6:36 a.m.