Triple
T12861492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | İZDENİZ |
E307600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal sea transportation company |
C220
|
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: municipal sea transportation company Context triple: [İZDENİZ, instanceOf, municipal sea transportation company]
-
A.
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.
-
B.
public transportation agency
chosen
A public transportation agency is an organization responsible for planning, operating, and managing shared transit services such as buses, trains, and other modes to provide mobility for the public within a defined region.
-
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.
transportation services company
A transportation services company is an organization that plans, manages, and operates the movement of people or goods using various modes of transport, such as road, rail, air, or sea, often providing logistics, scheduling, and support services.
-
E.
marine transit service
A marine transit service is an organized operation that transports passengers and/or cargo over water using vessels such as ferries, ships, or boats along scheduled or on-demand routes.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:37 p.m.