Triple
T2960583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Container Terminal Inc. |
E80037
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | container terminal operator |
C6404
|
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: container terminal operator Context triple: [New York Container Terminal Inc., instanceOf, container terminal operator]
-
A.
terminal multiplexer
A terminal multiplexer is a command-line tool that lets you create, manage, and switch between multiple terminal sessions within a single window or remote login.
-
B.
rancher
A rancher is a person who owns or manages a large farm or ranch, primarily raising livestock such as cattle, sheep, or horses for commercial purposes.
-
C.
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.
-
D.
transport infrastructure operator
chosen
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
-
E.
terminal emulator
A terminal emulator is a software application that replicates the functionality of a traditional hardware terminal, allowing users to interact with a computer’s command-line interface within a graphical or text-based environment.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:57 p.m.