Triple
T7076419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Wheeler |
E164830
|
entity |
| Predicate | hasGlacierRemnants |
P74856
|
FINISHED |
| Object | Pleistocene glaciation features |
—
|
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: Pleistocene glaciation features | Statement: [Mount Wheeler, hasGlacierRemnants, Pleistocene glaciation features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlacierRemnants Context triple: [Mount Wheeler, hasGlacierRemnants, Pleistocene glaciation features]
-
A.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
B.
hasGlaciatedPeak
Indicates that the subject has a peak that is covered or shaped by glacial ice.
-
C.
hasGlacierAccess
Indicates that an entity has direct access to, or is reachable from, a glacier (e.g., via paths, routes, or physical adjacency).
-
D.
liesNearGlacier
Indicates that one entity is located in close physical proximity to a glacier.
-
E.
notableGlacier
Indicates that the subject is a glacier recognized for its particular significance, prominence, or noteworthiness.
- F. None of above. chosen
Provenance (4 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ebf4048190bf5d7156817f93a7 |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:40 p.m.