Triple
T19511756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Ushba |
E488172
|
entity |
| Predicate | hasTwinPeak |
P73388
|
FINISHED |
| Object | South Ushba |
—
|
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: South Ushba | Statement: [North Ushba, hasTwinPeak, South Ushba]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: South Ushba Context triple: [North Ushba, hasTwinPeak, South Ushba]
-
A.
South Ushba
chosen
South Ushba is one of the twin summits of Mount Ushba in the Caucasus, known among climbers for its steep, challenging routes and dramatic alpine scenery.
-
B.
North Ushba
North Ushba is one of the twin summits of the dramatic, technically challenging Ushba peak in the Caucasus Mountains of Georgia.
-
C.
Ochuse
Ochuse is the historical name for the Spanish colonial settlement of Santa María de Ochuse, an early European outpost in what is now the Gulf Coast region of the United States.
-
D.
Ushba
Ushba is a striking double-summited peak in the Caucasus Mountains of Georgia, renowned among climbers for its technical difficulty and dramatic, spire-like profile.
-
E.
Northern Uma
Northern Uma is a regional dialect of the Uma language spoken by communities in Central Sulawesi, Indonesia.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359908fc8190bd05f26d4271d268 |
completed | April 20, 2026, 2:18 p.m. |
Created at: April 10, 2026, 1:40 p.m.