Triple
T155431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNECE Inland Transport Committee |
E3169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport policy body |
C1801
|
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: transport policy body Context triple: [UNECE Inland Transport Committee, instanceOf, transport policy body]
-
A.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
B.
navigator
A navigator is an entity responsible for determining and directing the optimal path or course from a starting point to a desired destination using available information and tools.
-
C.
public transportation agency
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.
-
D.
transport layer protocol
A transport layer protocol is a communication protocol that provides end-to-end data transfer services between applications across networked devices, handling functions like segmentation, reliability, flow control, and multiplexing.
-
E.
transport hub
A transport hub is a central location where multiple modes or routes of transportation intersect, enabling the efficient transfer of passengers or goods between them.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.