Triple
T9709196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakawan Range |
E234977
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Kangar |
E220278
|
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: Kangar | Statement: [Nakawan Range, locatedNear, Kangar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kangar Context triple: [Nakawan Range, locatedNear, Kangar]
-
A.
Kangar
chosen
Kangar is the main administrative and commercial center of the Malaysian state of Perlis.
-
B.
Kangha
Kangha is a small wooden comb that serves as one of the Five Ks in Sikhism, symbolizing cleanliness and discipline for initiated Sikhs.
-
C.
Rangloi
Rangloi is a regional dialect of the Kumaoni language spoken in parts of the Indian Himalayan region.
-
D.
Kandau
Kandau is a town in present-day Latvia historically known as the birthplace of the German experimental psychologist Oswald Külpe.
-
E.
Tangtse
Tangtse is a village in the Leh district of Ladakh, India, situated along key routes between the Indus Valley and the Pangong Tso region in the Himalayas.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da7c6188190b086f7e411378268 |
completed | April 1, 2026, 10:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f8476e08190865700679069dee6 |
completed | April 4, 2026, 11:32 p.m. |
Created at: March 30, 2026, 8:19 p.m.