Triple
T11107614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maleville |
E262673
|
entity |
| Predicate | vehicleRegistrationCodeDepartment |
P1173
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [Maleville, vehicleRegistrationCodeDepartment, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleRegistrationCodeDepartment Context triple: [Maleville, vehicleRegistrationCodeDepartment, 12]
-
A.
vehicleRegistrationAuthority
Indicates the authority or organization responsible for officially registering a vehicle and maintaining its registration records.
-
B.
vehicleRegistrationCode
chosen
Indicates the official registration identifier assigned to a vehicle, typically used for legal identification and record-keeping.
-
C.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
-
D.
cityDepartment
Indicates that one entity is a department that operates within, or is administratively part of, a particular city.
-
E.
hasCountyNumberPlateCode
Indicates that an entity (such as a vehicle or registration) bears a number plate code that corresponds to a specific county.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a6546d4819092187e9c12a30ed5 |
completed | April 9, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.