Triple
T29384773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karni crossing |
E745221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial border terminal |
C7781
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: commercial border terminal Context triple: [Karni crossing, instanceOf, commercial border terminal]
-
A.
cross-border terminal
chosen
A cross-border terminal is a transportation facility located at or near an international boundary that consolidates, processes, and transfers passengers or freight between different countries’ transport networks while handling customs, immigration, and regulatory controls.
-
B.
self-service banking terminal
A self-service banking terminal is an automated machine that allows customers to independently perform common banking transactions—such as withdrawals, deposits, transfers, and account inquiries—without assistance from bank staff.
-
C.
rail border crossing
A rail border crossing is a designated point where railway lines intersect an international boundary, enabling the controlled movement of trains, cargo, and passengers between countries.
-
D.
container terminal complex
A container terminal complex is a large, integrated facility where containerized cargo is transferred between ships, trucks, and trains, supported by specialized infrastructure, equipment, and logistics services.
-
E.
merchant enclave
A merchant enclave is a semi-autonomous district or settlement where traders from diverse regions concentrate to conduct commerce under specialized legal, economic, and cultural arrangements.
- F. None of above.
Provenance (1 batch)
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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:37 p.m.