Triple
T18262635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tustumena Glacier |
E437400
|
entity |
| Predicate | terminusForms |
P77353
|
FINISHED |
| Object | Tustumena Lake |
—
|
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: Tustumena Lake | Statement: [Tustumena Glacier, terminusForms, Tustumena Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusForms Context triple: [Tustumena Glacier, terminusForms, Tustumena Lake]
-
A.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
B.
terminusType
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
C.
terminusFeature
chosen
Indicates that a specific physical or structural feature is located at, marks, or characterizes the endpoint or terminus of something.
-
D.
terminusView
Indicates a perspective or representation that focuses on the endpoint or final destination of something.
-
E.
terminusDescription
Indicates the textual description that characterizes the endpoint or final stop of a route, path, or process.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff77882c81909774aefc57ccca3e |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.