Triple
T19390734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutiyana |
E485059
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | GJ-25 |
—
|
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: GJ-25 | Statement: [Kutiyana, vehicleRegistrationCode, GJ-25]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GJ-25 Context triple: [Kutiyana, vehicleRegistrationCode, GJ-25]
-
A.
GJ-25
chosen
GJ-25 is the vehicle registration code assigned to the Porbandar district in the Indian state of Gujarat.
-
B.
GJ-24
GJ-24 is the vehicle registration code assigned to motor vehicles registered in Patan district of Gujarat, India.
-
C.
GJ-20
GJ-20 is the motor vehicle registration code assigned to the Dahod district in the Indian state of Gujarat.
-
D.
GJ-18
GJ-18 is the vehicle registration code assigned to motor vehicles registered in Rajkot district in the Indian state of Gujarat.
-
E.
GJ-18
GJ-18 is the regional vehicle registration code assigned to motor vehicles registered in Gandhinagar, the capital city of Gujarat, India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b44b70c81908e2f0deeabe4360f |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.