Triple
T30304989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OAL |
E770756
|
entity |
| Predicate | licencePlateSystem |
P18660
|
FINISHED |
| Object | German vehicle registration system |
—
|
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: German vehicle registration system | Statement: [OAL, licencePlateSystem, German vehicle registration system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licencePlateSystem Context triple: [OAL, licencePlateSystem, German vehicle registration system]
-
A.
licensePlateSystem
chosen
Indicates a system or scheme used to assign, format, and manage license plate identifiers for vehicles.
-
B.
licensePlateReference
Indicates a reference or link from one entity to a specific vehicle license plate identifier.
-
C.
licensePlateLocation
Indicates the physical position or placement of a license plate on or relative to an object or vehicle.
-
D.
countryVehicleRegistrationSystem
Indicates a relationship where a country maintains or governs an official system for registering vehicles within its jurisdiction.
-
E.
vehicleRegistrationAuthority
Indicates the authority or organization responsible for officially registering a vehicle and maintaining its registration records.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 7:49 p.m.