Triple
T1160980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLIC |
E24488
|
entity |
| Predicate | energyFrontier |
P23068
|
FINISHED |
| Object | multi-TeV lepton collisions |
—
|
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: multi-TeV lepton collisions | Statement: [CLIC, energyFrontier, multi-TeV lepton collisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyFrontier Context triple: [CLIC, energyFrontier, multi-TeV lepton collisions]
-
A.
energyRegime
chosen
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
B.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
C.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
D.
beamEnergyAfterUpgrade
Indicates the energy level of a beam following an upgrade or enhancement to the system that produces or accelerates it.
-
E.
energyStage
Indicates the specific phase or level within an energy-related process, cycle, or transformation that an entity is currently in.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcb1915081908834ced85d09e299 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.