Triple
T24041470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bistritsa Glacier |
E595388
|
entity |
| Predicate | isGlacialFeatureOf |
P49182
|
FINISHED |
| Object | Livingston Island |
—
|
NE NERFINISHED |
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: Livingston Island | Statement: [Bistritsa Glacier, isGlacialFeatureOf, Livingston Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGlacialFeatureOf Context triple: [Bistritsa Glacier, isGlacialFeatureOf, Livingston Island]
-
A.
isGlacialLake
Indicates that a body of water is classified as a glacial lake, formed by the action or presence of glaciers.
-
B.
isGlaciologicallyRelatedTo
chosen
Indicates a relationship where two entities are connected through glaciological processes, features, or phenomena (such as ice dynamics, glacial formation, movement, or melt).
-
C.
isGlaciallyFed
Indicates that something (typically a body of water) receives its primary input or supply from melting glacial ice.
-
D.
glacierType
Indicates the specific classification or category of a glacier based on its form, dynamics, or setting.
-
E.
hasGlacialLake
Indicates that one entity possesses, contains, or is associated with a lake formed by glacial activity.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8da38548190b2cc04ce7960ef9c |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:57 p.m.