Triple
T14994752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HB |
E373926
|
entity |
| Predicate | licensePlatePosition |
P51042
|
FINISHED |
| Object | beginning of the plate number |
—
|
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: beginning of the plate number | Statement: [HB, licensePlatePosition, beginning of the plate number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licensePlatePosition Context triple: [HB, licensePlatePosition, beginning of the plate number]
-
A.
licensePlateReference
Indicates a reference or link from one entity to a specific vehicle license plate identifier.
-
B.
isOnLicensePlateBeforeNumber
chosen
Indicates that one element appears on a license plate in a position preceding a specified number.
-
C.
licensePlateSystem
Indicates a system or scheme used to assign, format, and manage license plate identifiers for vehicles.
-
D.
registrationPlateFormat
Indicates the specific pattern or structure that a vehicle’s registration plate must follow (such as the arrangement of letters, numbers, and symbols).
-
E.
licensePlateOrigin
Indicates that a vehicle’s license plate was issued or originates from a particular jurisdiction or region.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded716ebb481908224d2d4f7561b03 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.