Triple
T6225710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K1 beam line |
E139226
|
entity |
| Predicate | beamProductionMethod |
P35199
|
FINISHED |
| Object | secondary particles from proton–target interactions |
—
|
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: secondary particles from proton–target interactions | Statement: [K1 beam line, beamProductionMethod, secondary particles from proton–target interactions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beamProductionMethod Context triple: [K1 beam line, beamProductionMethod, secondary particles from proton–target interactions]
-
A.
beamParticle
Indicates that one entity directs or projects another entity as a beam-like stream or focused flow.
-
B.
beamExtractionMethod
Indicates the method or technique used to extract or generate a beam from a source.
-
C.
hasProductionMethod
chosen
Indicates that one entity is produced, created, or manufactured using the method, process, or technique specified by another entity.
-
D.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
E.
beamName
Indicates that an entity has or is associated with a specific beam identifier or label.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062d42c688190be4d8d8325d6daaa |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.