Triple
T1096154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEP |
E24275
|
entity |
| Predicate | LEP1EnergyRange |
P3955
|
FINISHED |
| Object | around 91 GeV centre-of-mass |
—
|
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: around 91 GeV centre-of-mass | Statement: [LEP, LEP1EnergyRange, around 91 GeV centre-of-mass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LEP1EnergyRange Context triple: [LEP, LEP1EnergyRange, around 91 GeV centre-of-mass]
-
A.
typicalEnergyRange
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.
hasBranchingRatioToLeptons
Indicates the proportion of a particle’s decays that result in leptons among all its possible decay channels.
-
D.
maximumProtonEnergy
Indicates the highest energy value that protons can attain in a given system, process, or context.
-
E.
designedCenterOfMassEnergy
chosen
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_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.