Triple
T3687246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorner Glacier |
E78253
|
entity |
| Predicate | hasTerminusType |
P9111
|
FINISHED |
| Object | land-terminating glacier |
—
|
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: land-terminating glacier | Statement: [Gorner Glacier, hasTerminusType, land-terminating glacier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminusType Context triple: [Gorner Glacier, hasTerminusType, land-terminating glacier]
-
A.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
-
B.
terminusType
chosen
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
C.
hasSubTerminal
Indicates that an entity includes or is associated with a subordinate or lower-level terminal element within a hierarchical structure.
-
D.
hasTerminalFunction
Indicates that something possesses a function or role specifically associated with an endpoint, boundary, or final stage within a system or process.
-
E.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4c7e2bc81909356c8b0ed90feed |
completed | March 8, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.