Triple
T18383041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Inylchek Glacier |
E446504
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Pobeda Peak |
—
|
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: Pobeda Peak | Statement: [North Inylchek Glacier, near, Pobeda Peak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pobeda Peak Context triple: [North Inylchek Glacier, near, Pobeda Peak]
-
A.
Pobeda Peak
chosen
Pobeda Peak is the highest mountain in the Tian Shan range of Central Asia, straddling the border between Kyrgyzstan and China and known for its extreme climbing difficulty and severe weather.
-
B.
Pobeda Peak
Pobeda Peak is the highest mountain in northeastern Siberia, located in Russia’s remote Chersky Range.
-
C.
Cheshnina Peak
Cheshnina Peak is a mountain summit located within Alaska’s Wrangell Mountains range.
-
D.
Domogled Peak
Domogled Peak is a prominent mountain summit in southwestern Romania’s Cerna Valley region, known for its scenic views and inclusion in the Domogled–Valea Cernei National Park.
-
E.
Ambaji Peak
Ambaji Peak is a prominent summit within the Girnar mountain range in Gujarat, India, known for its religious significance and scenic trekking routes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179c931c8190b1c7c8284f42f7b7 |
completed | April 19, 2026, 5:57 p.m. |
Created at: April 10, 2026, 10:45 a.m.