Triple
T24739873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linton Creek |
E618522
|
entity |
| Predicate | hasSourceGlacier |
P4580
|
FINISHED |
| Object | Linton Glacier |
—
|
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: Linton Glacier | Statement: [Linton Creek, hasSourceGlacier, Linton Glacier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceGlacier Context triple: [Linton Creek, hasSourceGlacier, Linton Glacier]
-
A.
hasGlacier
chosen
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
B.
hasGlacierArm
Indicates that a glacier possesses or extends into a subsidiary arm or branch of ice connected to it.
-
C.
hasGlacierOutlet
Indicates that a glacier has a specific outlet feature or location through which its ice or meltwater flows or exits.
-
D.
hasGlacierAccess
Indicates that an entity has direct access to, or is reachable from, a glacier (e.g., via paths, routes, or physical adjacency).
-
E.
hasGlacierRemnants
Indicates that a location or landform retains remaining parts or traces of a formerly larger glacier.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:04 a.m.