Triple
T5618773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Cwm |
E147545
|
entity |
| Predicate | glacialOrigin |
P8808
|
FINISHED |
| Object | formed by glacial erosion |
—
|
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: formed by glacial erosion | Statement: [Western Cwm, glacialOrigin, formed by glacial erosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glacialOrigin Context triple: [Western Cwm, glacialOrigin, formed by glacial erosion]
-
A.
glacierType
Indicates the specific classification or category of a glacier based on its form, dynamics, or setting.
-
B.
isGlaciologicallyRelatedTo
Indicates a relationship where two entities are connected through glaciological processes, features, or phenomena (such as ice dynamics, glacial formation, movement, or melt).
-
C.
glaciationCharacteristic
chosen
Indicates that one entity is a characteristic, feature, or property associated with the process or effects of glaciation of another entity.
-
D.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
E.
hasGlaciatedPeak
Indicates that the subject has a peak that is covered or shaped by glacial ice.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c021dd5d0081909d18d16596fac507 |
completed | March 22, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.