Triple
T1096036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M2 beam line |
E24273
|
entity |
| Predicate | beamEnergySource |
P5355
|
FINISHED |
| Object | 400 GeV SPS proton 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: 400 GeV SPS proton beam | Statement: [M2 beam line, beamEnergySource, 400 GeV SPS proton beam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beamEnergySource Context triple: [M2 beam line, beamEnergySource, 400 GeV SPS proton beam]
-
A.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
B.
primaryBeamSource
chosen
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
C.
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.
-
D.
beamCurrent
Indicates the amount of electric current carried by a directed beam (such as a particle or electron beam) in a system or experiment.
-
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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99ffb3481908cd168b6c58e1c6d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.