Triple
T1336127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Kobe |
E28753
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international port |
C6253
|
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: international port Context triple: [Port of Kobe, instanceOf, international port]
-
A.
international airport
An international airport is a large, complex transportation hub that facilitates the arrival, departure, and transfer of passengers and cargo between countries through scheduled and chartered flights, customs, immigration, and related services.
-
B.
international office
An international office is an organizational unit that manages and supports an institution’s global activities, partnerships, and services for international stakeholders.
-
C.
inland port
An inland port is a logistics and transportation hub located away from coastal seaports, typically along rivers, canals, or rail corridors, that facilitates the transfer, storage, and distribution of goods between different modes of transport.
-
D.
international terminal area
An international terminal area is a designated section of an airport where passengers check in, depart, arrive, and transit for international flights, including associated facilities such as customs, immigration, security, and boarding gates.
-
E.
international standard
An international standard is an agreed-upon set of rules, guidelines, or specifications established by recognized global bodies to ensure compatibility, safety, and quality across countries and industries.
- F. None of above. chosen
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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.