Triple
T15929316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morang District |
E386281
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Biratnagar |
E673838
|
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: Biratnagar | Statement: [Morang District, hasMajorCity, Biratnagar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Biratnagar Context triple: [Morang District, hasMajorCity, Biratnagar]
-
A.
Biratnagar
chosen
Biratnagar is a major industrial and commercial city in southeastern Nepal, serving as a key economic hub near the Indian border.
-
B.
Birgunj
Birgunj is a major commercial and industrial city in southern Nepal, serving as a key trade gateway with India.
-
C.
Nijgadh
Nijgadh is a town in southeastern Nepal notable for its location along the East–West Highway and as the proposed site of a major international airport.
-
D.
Nepalgunj
Nepalgunj is a major city in southwestern Nepal known as a commercial and transportation hub near the Indian border.
-
E.
Bhadrapur
Bhadrapur is a town in southeastern Nepal known as a key urban and commercial center near the Indian border in Jhapa District.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156a39abc8190927818f6e185033a |
completed | April 16, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffbe727c348190907c9e7a5db6031d |
completed | May 9, 2026, 11:08 p.m. |
Created at: April 10, 2026, 4:52 a.m.