Triple
T23269458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAMA/LIBRA |
E588247
|
entity |
| Predicate | energyRangeOfInterest |
P1457
|
FINISHED |
| Object | few keV region |
—
|
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: few keV region | Statement: [DAMA/LIBRA, energyRangeOfInterest, few keV region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyRangeOfInterest Context triple: [DAMA/LIBRA, energyRangeOfInterest, few keV region]
-
A.
typicalEnergyRange
chosen
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
B.
energyRangeUpperBound_MeV
Indicates the maximum energy value, expressed in mega–electronvolts (MeV), that defines the upper limit of an energy range in the relationship.
-
C.
energyIntegrationRange
Indicates the span of energy values over which a quantity (such as a function or signal) is integrated or accumulated.
-
D.
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.
-
E.
energyDomain
Indicates that one entity operates within, belongs to, or is characterized by a particular type or domain of energy associated with the other entity.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957219188190b30bceffad1542da |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:45 p.m.