Triple
T31473497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESB |
E802924
|
entity |
| Predicate | licencePlatePrefixFor |
P68833
|
FINISHED |
| Object | Neustadt an der Waldnaab district |
—
|
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: Neustadt an der Waldnaab district | Statement: [ESB, licencePlatePrefixFor, Neustadt an der Waldnaab district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licencePlatePrefixFor Context triple: [ESB, licencePlatePrefixFor, Neustadt an der Waldnaab district]
-
A.
hasVehicleLicensePrefix
chosen
Indicates that one entity has, uses, or is associated with a specific vehicle license plate prefix represented by the other entity.
-
B.
licensePlateLocation
Indicates the physical position or placement of a license plate on or relative to an object or vehicle.
-
C.
isOnLicensePlateBeforeNumber
Indicates that one element appears on a license plate in a position preceding a specified number.
-
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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:27 p.m.