Triple
T22695123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ND280 |
E561154
|
entity |
| Predicate | hasScientificPurpose |
P24615
|
FINISHED |
| Object | measure unoscillated neutrino beam |
—
|
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: measure unoscillated neutrino beam | Statement: [ND280, hasScientificPurpose, measure unoscillated neutrino beam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScientificPurpose Context triple: [ND280, hasScientificPurpose, measure unoscillated neutrino beam]
-
A.
hasScientificValue
Indicates that something possesses significance, usefulness, or merit within scientific research, understanding, or methodology.
-
B.
isScientific
Indicates that something pertains to or is based on systematic scientific methods, principles, or knowledge.
-
C.
hasScientificInterestIn
Indicates that one entity holds a scientific curiosity, concern, or research focus directed toward another entity.
-
D.
hasResearchUse
chosen
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
-
E.
hasScience
Indicates that an entity possesses, includes, or is associated with a particular scientific discipline, content, or attribute.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789d46c881908176bc8e26f366f6 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:14 p.m.