Triple
T4180891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pune Junction |
E88190
|
entity |
| Predicate | connectsTo |
P845
|
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: [Pune Junction, connectsTo, Ahmedabad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ahmedabad Context triple: [Pune Junction, connectsTo, 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.
Vadodara
Vadodara is a major city in western India known for its rich cultural heritage, educational institutions, and industrial development.
-
C.
Gandhinagar
Gandhinagar is a planned city in western India known for serving as the administrative and political center of the state of Gujarat.
-
D.
Bhuj
Bhuj is a historic city in the Kutch district of Gujarat, India, known for its rich cultural heritage, traditional handicrafts, and role as a regional commercial and administrative center.
-
E.
Indore
Indore is a major commercial and educational hub in central India, known for its vibrant markets, food culture, and rapidly growing urban infrastructure.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0304702c8190899cbb0e3e41b987 |
completed | March 9, 2026, 5:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be395356e88190ba6c4b228669e40c |
completed | March 21, 2026, 6:23 a.m. |
Created at: March 9, 2026, 3:45 p.m.