Triple
T3806468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spallation Neutron Source |
E93018
|
entity |
| Predicate | designProtonEnergy |
P5333
|
FINISHED |
| Object | 1 GeV |
—
|
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: 1 GeV | Statement: [Spallation Neutron Source, designProtonEnergy, 1 GeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designProtonEnergy Context triple: [Spallation Neutron Source, designProtonEnergy, 1 GeV]
-
A.
maximumProtonEnergy
chosen
Indicates the highest energy value that protons can attain in a given system, process, or context.
-
B.
designEnergy
Indicates that an entity is responsible for planning, specifying, or determining the energy-related characteristics or performance of another entity.
-
C.
beamEnergyAfterUpgrade
Indicates the energy level of a beam following an upgrade or enhancement to the system that produces or accelerates it.
-
D.
maximumProtonProtonCentreOfMassEnergy
Indicates the highest center-of-mass energy achievable in proton–proton collisions for a given experimental or physical setup.
-
E.
designedCenterOfMassEnergy
Indicates that one entity specifies the intended or planned center-of-mass energy at which another entity (such as an experiment, collider, or process) is meant to operate.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:16 p.m.