Triple
T35739785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeronomy of Ice in the Mesosphere |
E1033001
|
entity |
| Predicate | studiesAltitudeRange |
P183673
|
FINISHED |
| Object | about 80–85 km |
—
|
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 80–85 km | Statement: [Aeronomy of Ice in the Mesosphere, studiesAltitudeRange, about 80–85 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiesAltitudeRange Context triple: [Aeronomy of Ice in the Mesosphere, studiesAltitudeRange, about 80–85 km]
-
A.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
B.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
C.
altitudeRange_m
Indicates the range of altitudes, measured in meters, over which the relationship or condition holds.
-
D.
altitudeRangeReported
chosen
Indicates that a specific range of altitudes has been reported for an entity or event, rather than a single altitude value.
-
E.
highestCampAltitudeMetres
Indicates the maximum altitude in meters reached by any camp associated with the 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.