Triple
T38450299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIB |
E912154
|
entity |
| Predicate | licencePlateCategory |
P18660
|
FINISHED |
| Object | geographic code |
—
|
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: geographic code | Statement: [VIB, licencePlateCategory, geographic code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licencePlateCategory Context triple: [VIB, licencePlateCategory, geographic code]
-
A.
vehicleRegistrationCategory
Indicates the classification or type of registration assigned to a vehicle under a specific regulatory or administrative scheme.
-
B.
vehicleCode
Indicates a relationship where a specific code or identifier is assigned to or associated with a vehicle.
-
C.
licensePlateSystem
chosen
Indicates a system or scheme used to assign, format, and manage license plate identifiers for vehicles.
-
D.
homologationClass
Indicates the specific regulatory or competitive category under which something (typically a vehicle or product) has been officially approved or certified.
-
E.
vehicleRegistrationCode
Indicates the official registration identifier assigned to a vehicle, typically used for legal identification and record-keeping.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.