Triple
T2977116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NuSTAR |
E80423
|
entity |
| Predicate | energyResolution |
P7238
|
FINISHED |
| Object | about 400 eV at 10 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: about 400 eV at 10 keV | Statement: [NuSTAR, energyResolution, about 400 eV at 10 keV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyResolution Context triple: [NuSTAR, energyResolution, about 400 eV at 10 keV]
-
A.
spectralResolution
chosen
Indicates the fineness with which a system can distinguish or separate different wavelengths or frequencies within a spectrum.
-
B.
sensorResolution
Indicates the level of detail or precision with which a sensor can measure or distinguish changes in the observed quantity or environment.
-
C.
hasSpatialResolution
Indicates that something is characterized by a specific level of spatial detail or granularity at which it can represent or distinguish features in space.
-
D.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
E.
energyScaleBehavior
Indicates how a quantity or system changes or responds when the overall energy scale of the situation is varied.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad998c589c8190b4530f3fb8975187 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.