Triple
T4569757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continuous Electron Beam Accelerator Facility |
E123000
|
entity |
| Predicate | typicalBeamEnergyRange |
P1457
|
FINISHED |
| Object | 1 GeV to 12 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 to 12 GeV | Statement: [Continuous Electron Beam Accelerator Facility, typicalBeamEnergyRange, 1 GeV to 12 GeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBeamEnergyRange Context triple: [Continuous Electron Beam Accelerator Facility, typicalBeamEnergyRange, 1 GeV to 12 GeV]
-
A.
typicalEnergyRange
chosen
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
B.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
C.
beamEnergyUnit
Indicates the unit of measurement used to express the energy of a beam.
-
D.
hasTypicalBeam
Indicates that an entity is associated with a characteristic or standard type of beam it commonly uses or possesses.
-
E.
beamlineMedium
Indicates that one entity serves as the medium or material through which a beamline passes or operates in relation to 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c3eba48190af1fce6e1ca16943 |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.