Triple
T28828365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homestake solar neutrino experiment |
E727973
|
entity |
| Predicate | detectsFromSource |
P166507
|
FINISHED |
| Object | solar core |
—
|
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: solar core | Statement: [Homestake solar neutrino experiment, detectsFromSource, solar core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectsFromSource Context triple: [Homestake solar neutrino experiment, detectsFromSource, solar core]
-
A.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
B.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
C.
requiresSources
Indicates that something must be supported, justified, or validated by one or more external sources.
-
D.
requiresDetectionOf
Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
-
E.
sourceAvailable
Indicates that the underlying source code or origin of an entity is accessible or obtainable.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 28, 2026, 6:36 a.m.