Triple
T15485156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanahun District |
E377025
|
entity |
| Predicate | hasEthnicGroup |
P1898
|
FINISHED |
| Object | Chhetri |
E603786
|
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: Chhetri | Statement: [Tanahun District, hasEthnicGroup, Chhetri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chhetri Context triple: [Tanahun District, hasEthnicGroup, Chhetri]
-
A.
Chhetri
chosen
Chhetri are a traditionally high-caste Hindu community of Nepal, historically associated with the Kshatriya (warrior-ruler) varna and prominent in the country’s political and military spheres.
-
B.
Tharu
The Tharu are an indigenous ethnic group from the Terai region of Nepal and northern India, known for their distinct language, culture, and traditional agrarian lifestyle.
-
C.
Thakuri
Thakuri is a high-status Khas caste group of Nepal traditionally associated with nobility and ruling elites.
-
D.
Bahun
Bahun is a high-caste Hindu Brahmin community in Nepal traditionally associated with priestly and scholarly roles.
-
E.
Thapa
Thapa is a common Nepali surname historically associated with influential military and political families, including notable figures such as Bhimsen Thapa.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8e6ff08190b130b3a38f4190e7 |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3d4661088190bb53161247effcc4 |
completed | May 9, 2026, 1:57 p.m. |
Created at: April 10, 2026, 3:46 a.m.