Triple
T20547793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian vehicle registration plate system |
E504517
|
entity |
| Predicate | stateCodeLength |
P3820
|
FINISHED |
| Object | 2 letters |
—
|
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: 2 letters | Statement: [Indian vehicle registration plate system, stateCodeLength, 2 letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCodeLength Context triple: [Indian vehicle registration plate system, stateCodeLength, 2 letters]
-
A.
countryCodeLength
Indicates the number of characters that a given country code consists of.
-
B.
nationalDestinationCodeLengthRange
Indicates the allowed range of lengths (minimum and maximum number of digits) for national destination codes used within a telephone numbering plan.
-
C.
regionCodeType
chosen
Indicates the classification or format type used for a given region code within a coding or identification system.
-
D.
provinceNumber
Indicates a relationship where an entity is assigned a specific numerical identifier corresponding to a province.
-
E.
stateSubdivisionCode
Indicates the standardized code that identifies a specific subdivision (such as a state, province, or region) within a larger country or territory.
- 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_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. |
Created at: April 16, 2026, 11:38 a.m.