Triple
T17591567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kriva Palanka |
E428460
|
entity |
| Predicate | carPlateCode |
P62402
|
FINISHED |
| Object | KP |
—
|
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: KP | Statement: [Kriva Palanka, carPlateCode, KP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carPlateCode Context triple: [Kriva Palanka, carPlateCode, KP]
-
A.
vehicleRegistrationCode
Indicates the official registration identifier assigned to a vehicle, typically used for legal identification and record-keeping.
-
B.
registrationPlateFormat
Indicates the specific pattern or structure that a vehicle’s registration plate must follow (such as the arrangement of letters, numbers, and symbols).
-
C.
usesCodeOnPlates
chosen
Indicates that an entity applies or employs a specific code or coding system on plates.
-
D.
licensePlateLocation
Indicates the physical position or placement of a license plate on or relative to an object or vehicle.
-
E.
countryVehicleRegistrationSystem
Indicates a relationship where a country maintains or governs an official system for registering vehicles within its jurisdiction.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e79dac8190953a1ce8fc015b20 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.