Triple
T1160927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Proton Synchrotron |
E24487
|
entity |
| Predicate | hasBeamType |
P3956
|
FINISHED |
| Object | high-intensity 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: high-intensity proton beams | Statement: [Super Proton Synchrotron, hasBeamType, high-intensity proton beams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeamType Context triple: [Super Proton Synchrotron, hasBeamType, high-intensity proton beams]
-
A.
hasTypicalBeam
Indicates that an entity is associated with a characteristic or standard type of beam it commonly uses or possesses.
-
B.
beamType
chosen
Indicates the specific kind or category of beam involved in the relationship or action.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasBenchType
Indicates that an entity is associated with or characterized by a specific type or category of bench.
-
E.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
- 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.