Triple
T230729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proton Synchrotron |
E4404
|
entity |
| Predicate | injectionEnergyFromLinac |
P5351
|
FINISHED |
| Object | 50 MeV |
—
|
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: 50 MeV | Statement: [Proton Synchrotron, injectionEnergyFromLinac, 50 MeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: injectionEnergyFromLinac Context triple: [Proton Synchrotron, injectionEnergyFromLinac, 50 MeV]
-
A.
injectionEnergyTo
Indicates the amount of energy transferred or supplied from one entity to another through an injection process.
-
B.
commissionedAsLHCInjector
Indicates that an accelerator or facility was formally designated and brought into operation to serve as an injector for the Large Hadron Collider (LHC).
-
C.
beamEnergy
chosen
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
D.
replacedAcceleratorEnergy
Indicates that one accelerator energy value has been substituted or superseded by another in a given context.
-
E.
beamLine
Indicates a relationship where one entity directs or projects a beam or focused line (such as light, energy, or signal) toward another entity.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.