Triple
T582650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gujarat |
E15090
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Ahmedabad |
E14357
|
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: Ahmedabad | Statement: [Gujarat, hasMajorCity, Ahmedabad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ahmedabad Context triple: [Gujarat, hasMajorCity, Ahmedabad]
-
A.
Ahmedabad
chosen
Ahmedabad is a major city in the western Indian state of Gujarat, known for its rich history, textile industry, and role as an important economic and cultural center.
-
B.
Gandhinagar
Gandhinagar is a planned city in western India known for serving as the administrative and political center of the state of Gujarat.
-
C.
Surat
Surat is a historic port city in the Indian state of Gujarat that became an important center of trade and commerce during the Mughal and early colonial periods.
-
D.
Jaipur
Jaipur is a major historic city in northwestern India, famed for its pink-hued architecture, royal palaces, and role as a key cultural and tourist center.
-
E.
Rajkot
Rajkot is a major city in the Indian state of Gujarat, known as an important commercial and cultural center of the Saurashtra region.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b85becc8190b4d98c00e5fa7c04 |
completed | March 1, 2026, 8:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac3b93323c8190948dd9993a468a78 |
completed | March 7, 2026, 2:52 p.m. |
Created at: March 1, 2026, 7:33 p.m.