Triple
T29884599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikkim–Jhapa sector crossings |
E758974
|
entity |
| Predicate | locatedInNepalDistrict |
P29284
|
FINISHED |
| Object | Jhapa District |
—
|
NE NERFINISHED |
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: Jhapa District | Statement: [Sikkim–Jhapa sector crossings, locatedInNepalDistrict, Jhapa District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNepalDistrict Context triple: [Sikkim–Jhapa sector crossings, locatedInNepalDistrict, Jhapa District]
-
A.
locatedInBorderDistrictOnNepaliSide
Indicates that something is situated within a border district that lies on the Nepali side of an international boundary.
-
B.
regionTypeWithinSolukhumbu
Indicates that one region is classified as a specific type of region located within the Solukhumbu area.
-
C.
basedInDistrict
chosen
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
-
D.
locatedNearGovernmentDistrict
Indicates that one entity is situated close to or in the immediate vicinity of a government district.
-
E.
distanceFromKathmandu
Indicates the measured spatial distance between a given location or entity and the city of Kathmandu.
- F. None of above.
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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: April 29, 2026, 5:59 p.m.