Triple
T20547797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian vehicle registration plate system |
E504517
|
entity |
| Predicate | introducedHighSecurityPlates |
P140507
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Indian vehicle registration plate system, introducedHighSecurityPlates, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedHighSecurityPlates Context triple: [Indian vehicle registration plate system, introducedHighSecurityPlates, 2001]
-
A.
usedOnOfficialPlatesIn
Indicates that something is employed or displayed on official license plates within a specified jurisdiction or region.
-
B.
usesCodeOnPlates
Indicates that an entity applies or employs a specific code or coding system on plates.
-
C.
hasPlate
Indicates that one entity possesses, is equipped with, or includes a plate as part of its attributes or components.
-
D.
licensePlateSystem
Indicates a system or scheme used to assign, format, and manage license plate identifiers for vehicles.
-
E.
isOnLicensePlateBeforeNumber
Indicates that one element appears on a license plate in a position preceding a specified number.
- F. None of above. chosen
Provenance (4 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a2991ac8819089b8c2d70eb88952 |
completed | April 20, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:38 a.m.