Triple
T15829657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGILE gamma-ray mission |
E383835
|
entity |
| Predicate | energyRangeHardX |
P1457
|
FINISHED |
| Object | about 18 keV to 60 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 18 keV to 60 keV | Statement: [AGILE gamma-ray mission, energyRangeHardX, about 18 keV to 60 keV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyRangeHardX Context triple: [AGILE gamma-ray mission, energyRangeHardX, about 18 keV to 60 keV]
-
A.
energyRangeUpperBound_MeV
Indicates the maximum energy value, expressed in mega–electronvolts (MeV), that defines the upper limit of an energy range in the relationship.
-
B.
typicalEnergyRange
chosen
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
C.
energyRangeLowerBound_keV
Indicates the minimum energy value, in kilo–electron volts (keV), that defines the lower limit of an energy range for the relationship or measurement.
-
D.
showsHardnessOf
Indicates that something displays or reveals the degree of hardness possessed by another entity.
-
E.
hardness
Indicates the degree to which one entity resists being scratched, indented, or deformed by another.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e62aba8819090978801f4df73fe |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.