Triple
T30883410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jorum Glacier |
E786685
|
entity |
| Predicate | hasTerminusFeature |
P77353
|
FINISHED |
| Object | inlet |
—
|
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: inlet | Statement: [Jorum Glacier, hasTerminusFeature, inlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminusFeature Context triple: [Jorum Glacier, hasTerminusFeature, inlet]
-
A.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
-
B.
hasTerminusRole
Indicates that an entity participates in something specifically in the capacity of a terminus or endpoint role.
-
C.
terminusFeature
chosen
Indicates that a specific physical or structural feature is located at, marks, or characterizes the endpoint or terminus of something.
-
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.
hasOppositeTerminus
Indicates that one terminus (end point) of an entity is directly opposite or facing the terminus of another entity.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 29, 2026, 8:48 p.m.