Triple
T10815760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kongur Tagh |
E255223
|
entity |
| Predicate | alternateName |
P39
|
FINISHED |
| Object | Kongur |
E255223
|
NE 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: Kongur | Statement: [Kongur Tagh, alternateName, Kongur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kongur Context triple: [Kongur Tagh, alternateName, Kongur]
-
A.
Kungrad
Kungrad is a town in northwestern Uzbekistan that serves as an important local center within the autonomous Republic of Karakalpakstan.
-
B.
Tongelre
Tongelre is a district in the Dutch city of Eindhoven, known for its mix of residential neighborhoods, green spaces, and former industrial areas.
-
C.
Kungara
Kungara is an alternative name for the Fur language, a Nilo-Saharan language spoken primarily by the Fur people of western Sudan.
-
D.
Kongur Tagh
chosen
Kongur Tagh is a massive, glaciated peak in western China that ranks among the highest mountains in the world and dominates the eastern edge of the Pamir region.
-
E.
Kangar
Kangar is the main administrative and commercial center of the Malaysian state of Perlis.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733edab248190b2cf7f7bc2684468 |
completed | April 9, 2026, 5:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de855799748190b51745a198daa8d0 |
completed | April 14, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:18 p.m.