Triple
T4468502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERN AWAKE experiment beamline |
E98436
|
entity |
| Predicate | secondaryBeamType |
P3956
|
FINISHED |
| Object | electron beam |
—
|
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: electron beam | Statement: [CERN AWAKE experiment beamline, secondaryBeamType, electron beam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryBeamType Context triple: [CERN AWAKE experiment beamline, secondaryBeamType, electron beam]
-
A.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
B.
beamParticle
Indicates that one entity directs or projects another entity as a beam-like stream or focused flow.
-
C.
usesPrimaryBeam
Indicates that one entity employs another entity as its main or principal beam in an operation or structure.
-
D.
beamType
chosen
Indicates the specific kind or category of beam involved in the relationship or action.
-
E.
secondaryTarget
Indicates that an entity serves as an additional or subordinate target in relation to a primary target within a given context or action.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:34 p.m.