Triple
T11970957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johns Hopkins Glacier |
E284916
|
entity |
| Predicate | hasIceCliffsHeight |
P18448
|
FINISHED |
| Object | tens of 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: tens of meters above sea level | Statement: [Johns Hopkins Glacier, hasIceCliffsHeight, tens of meters above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIceCliffsHeight Context triple: [Johns Hopkins Glacier, hasIceCliffsHeight, tens of meters above sea level]
-
A.
hasCliffHeight
chosen
Indicates the relationship between a cliff and the measurement of its vertical height.
-
B.
hasCliffsOn
Indicates that one entity possesses or features cliffs located along or on the surface of another entity.
-
C.
hasCliffs
Indicates that something possesses or is characterized by the presence of cliffs.
-
D.
hasCliffHeightCategory
Indicates the categorized height range of a cliff associated with an entity.
-
E.
hasCliff
Indicates that something possesses or features a steep, high rock face or abrupt vertical drop as part of its structure or environment.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037d32e88190b1509285dc907d29 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.