Triple
T26057015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FL |
E657143
|
entity |
| Predicate | vehicleCodeFor |
P62402
|
FINISHED |
| Object | Flensburg |
—
|
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: Flensburg | Statement: [FL, vehicleCodeFor, Flensburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleCodeFor Context triple: [FL, vehicleCodeFor, Flensburg]
-
A.
vehicleRegistrationCode
Indicates the official registration identifier assigned to a vehicle, typically used for legal identification and record-keeping.
-
B.
vehicleRegistrationCategory
Indicates the classification or type of registration assigned to a vehicle under a specific regulatory or administrative scheme.
-
C.
chassisCode
Indicates the specific chassis designation or code assigned to a vehicle model to distinguish its underlying structural platform or variant.
-
D.
usesCodeOnPlates
chosen
Indicates that an entity applies or employs a specific code or coding system on plates.
-
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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 7:11 p.m.