Triple
T29575445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunauli–Bhairahawa crossing |
E753430
|
entity |
| Predicate | hasImmigrationCheckpost |
P7852
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Sunauli–Bhairahawa crossing, hasImmigrationCheckpost, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImmigrationCheckpost Context triple: [Sunauli–Bhairahawa crossing, hasImmigrationCheckpost, yes]
-
A.
hasCustomsAndImmigration
chosen
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
B.
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.
-
C.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
D.
hasBorderControlBy
Indicates that the border of one entity is monitored, regulated, or managed by another entity.
-
E.
hasBorderControlHistory
Indicates that there is a documented history of actions, policies, or events related to border control involving the associated entities.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 6:02 p.m.