Triple
T28828258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homestake experiment |
E727970
|
entity |
| Predicate | detectedParticle |
P53467
|
FINISHED |
| Object | electron neutrino |
—
|
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 neutrino | Statement: [Homestake experiment, detectedParticle, electron neutrino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectedParticle Context triple: [Homestake experiment, detectedParticle, electron neutrino]
-
A.
usedParticle
Indicates that one entity employs or applies a particular particle (e.g., subatomic, linguistic, or material) in some process, context, or construction involving another entity.
-
B.
detected
chosen
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or event.
-
C.
beamParticle
Indicates that one entity directs or projects another entity as a beam-like stream or focused flow.
-
D.
detectedNeutrinoSource
Indicates that a particular source has been observed and identified as emitting detectable neutrinos.
-
E.
associatedWithParticle
Indicates that an entity has a contextual or functional connection to a specific particle (such as a subatomic particle or grammatical particle).
- 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_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:36 a.m.