Triple
T551951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LHC injector chain |
E11858
|
entity |
| Predicate | providesBeamEnergyRange |
P1457
|
FINISHED |
| Object | from MeV scale to hundreds of 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: from MeV scale to hundreds of GeV | Statement: [LHC injector chain, providesBeamEnergyRange, from MeV scale to hundreds of GeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesBeamEnergyRange Context triple: [LHC injector chain, providesBeamEnergyRange, from MeV scale to hundreds of GeV]
-
A.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
B.
typicalEnergyRange
chosen
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
C.
hasTypicalBeam
Indicates that an entity is associated with a characteristic or standard type of beam it commonly uses or possesses.
-
D.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499047bd4819089ca8345f1b6e46c |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bae210819093c2e0d33a8ca51a |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.