Triple
T1529687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kathmandu |
E32411
|
entity |
| Predicate | ethnicGroup |
P194
|
FINISHED |
| Object | Newar |
E133168
|
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: Newar | Statement: [Kathmandu, ethnicGroup, Newar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Newar Context triple: [Kathmandu, ethnicGroup, Newar]
-
A.
Newar language
chosen
The Newar language is an indigenous Sino-Tibetan language of Nepal, historically associated with the Newar people and the Kathmandu Valley’s rich literary and cultural traditions.
-
B.
Nepali
Nepali is an Indo-Aryan language primarily spoken in Nepal and parts of India, serving as Nepal’s official language and a major lingua franca of the Himalayan region.
-
C.
Garhwali
Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
-
D.
Tibetan
Tibetan is a Sino-Tibetan language spoken primarily in Tibet and surrounding Himalayan regions, serving as the liturgical language of Tibetan Buddhism and a key marker of Tibetan cultural identity.
-
E.
Kurukh
Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb1dfd1a48190804ca5f0fb6f5985 |
completed | March 7, 2026, 5:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad30942dc481908de85bd2ca30c0bd |
completed | March 8, 2026, 8:17 a.m. |
Created at: March 4, 2026, 7:26 p.m.