Triple
T3844052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union County, Tennessee |
E93523
|
entity |
| Predicate | licensePlateCode |
P26915
|
FINISHED |
| Object | Union |
—
|
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: Union | Statement: [Union County, Tennessee, licensePlateCode, Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licensePlateCode Context triple: [Union County, Tennessee, licensePlateCode, Union]
-
A.
licensePlateSystem
Indicates a system or scheme used to assign, format, and manage license plate identifiers for vehicles.
-
B.
vehicleRegistrationCode
Indicates the official registration identifier assigned to a vehicle, typically used for legal identification and record-keeping.
-
C.
isOnLicensePlateBeforeNumber
Indicates that one element appears on a license plate in a position preceding a specified number.
-
D.
roadSignCode
Indicates the specific regulatory or informational code assigned to a road sign that defines its meaning or instruction.
-
E.
hasCountyNumberPlateCode
chosen
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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb4fd308190a636ba9dbbe57ed6 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.