Triple
T29836661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Transport Offices in Kerala |
E757674
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road transport authority |
C43763
|
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: road transport authority Context triple: [Regional Transport Offices in Kerala, instanceOf, road transport authority]
-
A.
Regional Transport Office
chosen
A Regional Transport Office is a government agency responsible for vehicle registration, driver licensing, enforcement of transport regulations, and maintenance of regional motor vehicle records.
-
B.
road transport regulatory body
A road transport regulatory body is an authority responsible for setting, implementing, and enforcing rules, standards, and policies governing the safe, efficient, and sustainable operation of road transport systems.
-
C.
traffic authority
A traffic authority is an organization or governmental body responsible for planning, regulating, and managing road use, traffic flow, and transportation safety within a specific jurisdiction.
-
D.
state transport department
A state transport department is a government agency responsible for planning, regulating, and managing transportation systems and infrastructure within a state, including roads, public transit, and vehicle services.
-
E.
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.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:37 p.m.