Triple
T401486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | drift tube linac |
E9292
|
entity |
| Predicate | usesFrequencyRange |
P1685
|
FINISHED |
| Object | tens to hundreds of megahertz |
—
|
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: tens to hundreds of megahertz | Statement: [drift tube linac, usesFrequencyRange, tens to hundreds of megahertz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFrequencyRange Context triple: [drift tube linac, usesFrequencyRange, tens to hundreds of megahertz]
-
A.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
B.
frequencyRequirement
Indicates a constraint specifying how often an action, event, or condition must occur within a given context or time frame.
-
C.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
D.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
E.
vocalRange
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec9f77888190bcc2bc68d201ed35 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96ee4ec8190a5c0e3f491d3963d |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.