Triple
T1161107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point 5 of the LHC ring |
E24491
|
entity |
| Predicate | collides |
P12942
|
FINISHED |
| Object | proton beams |
—
|
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: proton beams | Statement: [Point 5 of the LHC ring, collides, proton beams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collides Context triple: [Point 5 of the LHC ring, collides, proton beams]
-
A.
collidesWith
chosen
Indicates that two entities come into contact with each other in space, typically implying an impact or physical intersection of their paths or volumes.
-
B.
collider
Indicates that two or more entities participate together in operating or utilizing a particle collider or similar high-energy physics experimental facility.
-
C.
collisionType
Indicates the specific kind or category of collision that occurs between two or more entities.
-
D.
collisionSystem
Indicates a physical interaction where two or more entities impact or collide with each other within a defined system or environment.
-
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_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.