Triple
T21003145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNL E852 |
E517345
|
entity |
| Predicate | usedBeamIntensity |
P142438
|
FINISHED |
| Object | high-intensity pion 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: high-intensity pion beam | Statement: [BNL E852, usedBeamIntensity, high-intensity pion beam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBeamIntensity Context triple: [BNL E852, usedBeamIntensity, high-intensity pion beam]
-
A.
usesPrimaryBeam
Indicates that one entity employs another entity as its main or principal beam in an operation or structure.
-
B.
providedBeamTo
Indicates that one entity supplied or delivered a beam (such as a structural or energy beam) to another entity.
-
C.
usesSpotBeams
Indicates that an entity employs focused, narrow beams (spot beams) to transmit or receive signals or energy.
-
D.
beamUse
Indicates the action of directing or emitting a beam (such as light, energy, or signal) from one entity toward a target or in a specific direction.
-
E.
beamCurrent
Indicates the amount of electric current carried by a directed beam (such as a particle or electron beam) in a system or experiment.
- F. None of above. chosen
Provenance (4 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc38b8688190860fba1b58e1b3e6 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:52 p.m.