Triple
T36917539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rangpo |
E913082
|
entity |
| Predicate | hasBorderCheckPostWith |
P39987
|
FINISHED |
| Object | West Bengal |
—
|
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: West Bengal | Statement: [Rangpo, hasBorderCheckPostWith, West Bengal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderCheckPostWith Context triple: [Rangpo, hasBorderCheckPostWith, West Bengal]
-
A.
hasBorderPostWith
chosen
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
B.
hasBorderControlBy
Indicates that the border of one entity is monitored, regulated, or managed by another entity.
-
C.
hasCustomsCheckpoint
Indicates that a location or route includes an official customs inspection point where goods, vehicles, or people are checked for compliance with border regulations.
-
D.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
-
E.
hasBorderCrossing
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.