Triple
T26535014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tambak Johor |
E671221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border link |
C9303
|
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: cross-border link Context triple: [Tambak Johor, instanceOf, cross-border link]
-
A.
cross-border transport link
chosen
A cross-border transport link is an infrastructure connection—such as a road, railway, bridge, tunnel, or ferry route—that enables the movement of people and goods between two or more countries.
-
B.
cross-border area
A cross-border area is a geographic region that spans across the boundaries of two or more countries, where social, economic, environmental, and political interactions occur and are often managed through cooperative arrangements.
-
C.
cross-border institution
A cross-border institution is an organization or entity that operates across national boundaries, coordinating policies, activities, or services between multiple countries or jurisdictions.
-
D.
cross‑border operation
A cross-border operation is an organized activity or transaction conducted across the legal, regulatory, or geographic boundaries of two or more countries.
-
E.
cross-border terminal
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.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:38 a.m.