Triple
T13300575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamma-ray Burst Monitor |
E316799
|
entity |
| Predicate | energyRangeUpper |
P108906
|
FINISHED |
| Object | about 40 MeV |
—
|
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 40 MeV | Statement: [Gamma-ray Burst Monitor, energyRangeUpper, about 40 MeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyRangeUpper Context triple: [Gamma-ray Burst Monitor, energyRangeUpper, about 40 MeV]
-
A.
energyHigherThan
Indicates that one entity possesses a greater amount or level of energy than another entity.
-
B.
energyRangeUpperBound_MeV
chosen
Indicates the maximum energy value, expressed in mega–electronvolts (MeV), that defines the upper limit of an energy range in the relationship.
-
C.
ageRangeUpper
Indicates the maximum age limit that bounds the upper end of an age range associated with an entity or relationship.
-
D.
isHighestRangeOf
Indicates that one entity represents the maximum or topmost range or interval within which another entity falls or is categorized.
-
E.
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.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:28 p.m.