Triple
T12861655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | İZDENİZ Maritime Transportation Services |
E307607
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public maritime transport operator |
C31979
|
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: public maritime transport operator Context triple: [İZDENİZ Maritime Transportation Services, instanceOf, public maritime transport operator]
-
A.
shipowner
A shipowner is an individual or entity that holds legal ownership of a vessel and is responsible for its operation, maintenance, and commercial employment.
-
B.
container shipping company
A container shipping company is a business that transports standardized cargo containers across oceans and other waterways using a fleet of specialized vessels, managing logistics, routing, and port operations.
-
C.
ship management company
A ship management company is an organization that oversees the technical, crewing, operational, and commercial management of vessels on behalf of ship owners to ensure safe, efficient, and compliant maritime operations.
-
D.
mass transit operator
A mass transit operator is an entity responsible for managing, coordinating, and providing public transportation services such as buses, trains, or subways within a specific region or network.
-
E.
transport infrastructure operator
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.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:37 p.m.