Triple
T1393430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevado San Francisco |
E30611
|
entity |
| Predicate | hasGlacialEvidence |
P22640
|
FINISHED |
| Object | moraines |
—
|
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: moraines | Statement: [Nevado San Francisco, hasGlacialEvidence, moraines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlacialEvidence Context triple: [Nevado San Francisco, hasGlacialEvidence, moraines]
-
A.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
B.
hasGeologicalEvidenceOf
chosen
Indicates that there is geological data or features supporting the existence, occurrence, or impact of a specified phenomenon or event.
-
C.
hasProglacialLake
Indicates that a glacier or ice sheet is or was associated with a lake formed directly in front of it by meltwater or ice-dammed water.
-
D.
glaciationCharacteristic
Indicates that one entity is a characteristic, feature, or property associated with the process or effects of glaciation of another entity.
-
E.
notableGlacier
Indicates that the subject is a glacier recognized for its particular significance, prominence, or noteworthiness.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c37cd99081908d16014e0b99992d |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.