Triple
T15069108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uhuru Peak |
E379828
|
entity |
| Predicate | hasOxygenLevel |
P87949
|
FINISHED |
| Object | significantly lower than sea level |
—
|
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: significantly lower than sea level | Statement: [Uhuru Peak, hasOxygenLevel, significantly lower than sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOxygenLevel Context triple: [Uhuru Peak, hasOxygenLevel, significantly lower than sea level]
-
A.
oxygenValueApprox
Indicates that the oxygen value of an entity is approximately equal to a specified reference value, within an acceptable margin of error.
-
B.
usedSupplementaryOxygen
Indicates that an entity received or utilized additional oxygen support beyond normal atmospheric breathing, typically via medical equipment.
-
C.
oxygenRequirement
Indicates the level or type of oxygen needed by an entity to live, function, or operate.
-
D.
carbonDioxideLevel
Indicates the measured concentration or amount of carbon dioxide present in a given environment or system.
-
E.
oxygenLevelAtSummit
chosen
Indicates the amount or concentration of oxygen present at the summit of a specified location or peak.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedeebc7e48190a86b4f0afe8844bb |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.