Triple
T12175139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spektr-RG |
E290067
|
entity |
| Predicate | ART-XC_energyRange |
P1457
|
FINISHED |
| Object | 4–30 keV |
—
|
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: 4–30 keV | Statement: [Spektr-RG, ART-XC_energyRange, 4–30 keV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ART-XC_energyRange Context triple: [Spektr-RG, ART-XC_energyRange, 4–30 keV]
-
A.
typicalEnergyRange
chosen
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
B.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
C.
energyConcentration
Indicates a relationship where energy is gathered, focused, or accumulated within a specific region, object, or system.
-
D.
energyDependence
Indicates that one entity’s state, behavior, or outcome is contingent on or influenced by the amount, source, or availability of energy associated with another entity.
-
E.
hasOrderOfMagnitudeInElectronvolts
Indicates that one quantity has an energy scale whose order of magnitude is expressed in electronvolts (eV) relative to another value or reference.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.