Triple
T12162404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Gujarat |
E289740
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Navsari |
E360080
|
NE 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: Navsari | Statement: [South Gujarat, majorCity, Navsari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Navsari Context triple: [South Gujarat, majorCity, Navsari]
-
A.
Navsari
chosen
Navsari is a city in the Indian state of Gujarat known historically as a center of Parsi culture and commerce.
-
B.
Naupada
Naupada is a prominent residential and commercial locality within the city of Thane in Maharashtra, India.
-
C.
Marvadi
Marvadi is an alternative name for the Marwari people and their Indo-Aryan language traditionally associated with the Marwar region of Rajasthan, India.
-
D.
Veraval
Veraval is a coastal city in the Indian state of Gujarat, known historically as a major fishing and port town near the pilgrimage center of Somnath.
-
E.
Navalgund
Navalgund is a town in the Indian state of Karnataka known for its traditional handloom cotton and silk sarees, especially the distinctive Navalgund durries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915c498a081908389598d0c247505 |
completed | April 10, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62a84236c8190baa383c950d2bd62 |
completed | May 2, 2026, 4:47 p.m. |
Created at: April 8, 2026, 9:50 p.m.