Triple
T3616129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NuMI beamline |
E76603
|
entity |
| Predicate | beamPower |
P39191
|
FINISHED |
| Object | up to ~700 kW class |
—
|
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: up to ~700 kW class | Statement: [NuMI beamline, beamPower, up to ~700 kW class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beamPower Context triple: [NuMI beamline, beamPower, up to ~700 kW class]
-
A.
powerOutputW
chosen
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
B.
beamCurrent
Indicates the amount of electric current carried by a directed beam (such as a particle or electron beam) in a system or experiment.
-
C.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
D.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
-
E.
powerFeeding
Indicates a relationship where one entity supplies electrical power to another entity for its operation or charging.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27c98088190a493c9eddf6b206a |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.