Triple
T34524466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dharbandora |
E886362
|
entity |
| Predicate | vehicleRegistrationCodeOfState |
P1173
|
FINISHED |
| Object | GA |
—
|
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: GA | Statement: [Dharbandora, vehicleRegistrationCodeOfState, GA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleRegistrationCodeOfState Context triple: [Dharbandora, vehicleRegistrationCodeOfState, GA]
-
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.
vehicleCode
Indicates a relationship where a specific code or identifier is assigned to or associated with a vehicle.
-
D.
vehicleRegistrationAuthority
Indicates the authority or organization responsible for officially registering a vehicle and maintaining its registration records.
-
E.
licensePlateLocation
Indicates the physical position or placement of a license plate on or relative to an object or vehicle.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:02 a.m.