Triple
T2208395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ForwArd Search ExpeRiment |
E50855
|
entity |
| Predicate | collisionEnergyContext |
P23072
|
FINISHED |
| Object | high-energy proton–proton 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: high-energy proton–proton collisions | Statement: [ForwArd Search ExpeRiment, collisionEnergyContext, high-energy proton–proton collisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collisionEnergyContext Context triple: [ForwArd Search ExpeRiment, collisionEnergyContext, high-energy proton–proton collisions]
-
A.
collisionType
Indicates the specific kind or category of collision that occurs between two or more entities.
-
B.
centerOfMassEnergy
chosen
Indicates the total energy available in the center-of-mass frame when two or more particles interact or collide.
-
C.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
D.
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.
-
E.
collisionDomain
Indicates that two or more network entities share the same collision domain, meaning their transmissions can interfere and cause packet collisions with each other.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1baa0948190b07ffc347a4f714e |
completed | March 7, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69abbda8a6dc8190aa855ce2d17194b1 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.