Triple
T30016864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaigaon–Phuentsholing border crossing |
E762618
|
entity |
| Predicate | nearbyMajorCityInIndia |
P1982
|
FINISHED |
| Object | Siliguri |
—
|
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: Siliguri | Statement: [Jaigaon–Phuentsholing border crossing, nearbyMajorCityInIndia, Siliguri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMajorCityInIndia Context triple: [Jaigaon–Phuentsholing border crossing, nearbyMajorCityInIndia, Siliguri]
-
A.
nearbyIndianTown
Indicates that one location is a town in India situated close to the referenced place.
-
B.
areaRankInIndia
Indicates the relative position of an entity when all entities in India are ordered by their area size.
-
C.
nearestMajorRiverTown
Indicates that one town is the closest significant river-based settlement to another location or town.
-
D.
nearestMajorCity
chosen
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
-
E.
majorCityNearMouth
Indicates that a major city is located close to the mouth (outflow point) of a river.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 29, 2026, 6:46 p.m.