Triple
T37113789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MH-02 |
E919063
|
entity |
| Predicate | belongsToVehicleRegistrationRegion |
P119126
|
FINISHED |
| Object | Mumbai RTO regions |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Mumbai RTO regions | Statement: [MH-02, belongsToVehicleRegistrationRegion, Mumbai RTO regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToVehicleRegistrationRegion Context triple: [MH-02, belongsToVehicleRegistrationRegion, Mumbai RTO regions]
-
A.
countryVehicleRegistrationSystem
Indicates a relationship where a country maintains or governs an official system for registering vehicles within its jurisdiction.
-
B.
appliesToVehicleRegistration
Indicates that something (such as a rule, fee, document, or condition) is relevant or applicable to a specific vehicle registration.
-
C.
vehicleRegistrationAuthority
Indicates the authority or organization responsible for officially registering a vehicle and maintaining its registration records.
-
D.
vehicleRegistrationLocation
Indicates the place or jurisdiction where a vehicle is officially registered.
-
E.
registrationRegion
chosen
Indicates the geographic or administrative region in which an entity is officially registered.
- F. None of above.
Provenance (3 batches)
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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: May 3, 2026, 4:15 p.m.