Triple
T9770392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | neutrino hypothesis |
E237108
|
entity |
| Predicate | eventuallyConfirmedBy |
P653
|
FINISHED |
| Object | neutrino detection experiments |
—
|
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: neutrino detection experiments | Statement: [neutrino hypothesis, eventuallyConfirmedBy, neutrino detection experiments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventuallyConfirmedBy Context triple: [neutrino hypothesis, eventuallyConfirmedBy, neutrino detection experiments]
-
A.
confirmedBy
chosen
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
B.
confirmedFor
Indicates that an entity has been officially approved, scheduled, or validated to participate in, receive, or be associated with another specified entity or event.
-
C.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
D.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
E.
discoveryConfirmed
Indicates that a previously identified potential discovery has been verified as valid or true.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f1dea08190b89bcc192b068c66 |
completed | April 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.