Triple
T13349881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth's atmosphere |
E318041
|
entity |
| Predicate | ionosphereLocatedIn |
P9997
|
FINISHED |
| Object | thermosphere |
—
|
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: thermosphere | Statement: [Earth's atmosphere, ionosphereLocatedIn, thermosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ionosphereLocatedIn Context triple: [Earth's atmosphere, ionosphereLocatedIn, thermosphere]
-
A.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
B.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
C.
capturesAtmosphereOf
Indicates that one entity successfully conveys or reflects the overall mood, tone, or ambiance characteristic of another entity.
-
D.
usesAtmosphereOf
Indicates that one entity makes use of or operates within the atmospheric conditions or composition associated with another entity.
-
E.
spacecraftLocated
Indicates that a spacecraft is situated at, or associated with, a specific location or celestial body.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8c2f1c819094f0970f35f18afa |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.