Triple
T3978959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea of Ice |
E85709
|
entity |
| Predicate | upperBasinElevation |
P19320
|
FINISHED |
| Object | over 3000 meters above 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: over 3000 meters above sea level | Statement: [Sea of Ice, upperBasinElevation, over 3000 meters above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperBasinElevation Context triple: [Sea of Ice, upperBasinElevation, over 3000 meters above sea level]
-
A.
highestElevationApprox
chosen
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
B.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
C.
elevationAboveLake
Indicates the vertical height or altitude of something relative to the surface level of a specified lake.
-
D.
reservoirElevation
Indicates the height or level of water stored in a reservoir relative to a defined reference point.
-
E.
rankInNorthAmericaByElevation
Indicates the relative position of a place in an ordered list of locations in North America based on their elevation.
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.