Triple
T7318845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevado Tres Cruces |
E168484
|
entity |
| Predicate | isExtensivelyGlaciated |
P4580
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nevado Tres Cruces, isExtensivelyGlaciated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExtensivelyGlaciated Context triple: [Nevado Tres Cruces, isExtensivelyGlaciated, true]
-
A.
hasGlaciatedPeak
Indicates that the subject has a peak that is covered or shaped by glacial ice.
-
B.
isMostExtensiveGlaciationIn
Indicates that a particular glaciation event is the largest or most widespread one occurring within a specified region or geological context.
-
C.
hasGlacier
chosen
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
D.
isGlaciologicallyRelatedTo
Indicates a relationship where two entities are connected through glaciological processes, features, or phenomena (such as ice dynamics, glacial formation, movement, or melt).
-
E.
hasGlacialLake
Indicates that one entity possesses, contains, or is associated with a lake formed by glacial activity.
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef18b7bc81908a9ee405d684f304 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.