Triple
T29884598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikkim–Jhapa sector crossings |
E758974
|
entity |
| Predicate | locatedInNepalProvince |
P182217
|
FINISHED |
| Object | Koshi Province |
—
|
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: Koshi Province | Statement: [Sikkim–Jhapa sector crossings, locatedInNepalProvince, Koshi Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNepalProvince Context triple: [Sikkim–Jhapa sector crossings, locatedInNepalProvince, Koshi Province]
-
A.
regionTypeWithinSolukhumbu
Indicates that one region is classified as a specific type of region located within the Solukhumbu area.
-
B.
locatedInBorderDistrictOnNepaliSide
Indicates that something is situated within a border district that lies on the Nepali side of an international boundary.
-
C.
entryPointFromNepal
Indicates that something serves as an entry point or access route originating from Nepal.
-
D.
stationedInProvince
Indicates that an entity is assigned or based in a particular province as its location or area of operation.
-
E.
positionWithinProvince
chosen
Indicates that one entity’s location lies inside the geographic or administrative boundaries of a specified province.
- 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_6a00694f72888190983fee7d687a6daa |
completed | May 10, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_6a00685dbf44819098ea0c86bb9e50d8 |
completed | May 10, 2026, 11:13 a.m. |
Created at: April 29, 2026, 5:59 p.m.