Triple
T30667940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Vöslau |
E780712
|
entity |
| Predicate | vehicleRegistrationPlateCode |
P1173
|
FINISHED |
| Object | BN |
—
|
NE NERFINISHED |
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: BN | Statement: [Bad Vöslau, vehicleRegistrationPlateCode, BN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleRegistrationPlateCode Context triple: [Bad Vöslau, vehicleRegistrationPlateCode, BN]
-
A.
vehicleRegistrationCode
chosen
Indicates the official registration identifier assigned to a vehicle, typically used for legal identification and record-keeping.
-
B.
countryVehicleRegistrationSystem
Indicates a relationship where a country maintains or governs an official system for registering vehicles within its jurisdiction.
-
C.
licensePlateLocation
Indicates the physical position or placement of a license plate on or relative to an object or vehicle.
-
D.
usesCodeOnPlates
Indicates that an entity applies or employs a specific code or coding system on plates.
-
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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:31 p.m.