Triple
T12370965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambay region of Gujarat |
E294998
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Khambhat |
E993457
|
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: Khambhat | Statement: [Cambay region of Gujarat, hasPort, Khambhat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khambhat Context triple: [Cambay region of Gujarat, hasPort, Khambhat]
-
A.
Khambhat
chosen
Khambhat is a historic coastal town in Gujarat, India, known for its ancient port, trade heritage, and distinctive gulf on the Arabian Sea.
-
B.
Khargone
Khargone is a city in western Madhya Pradesh, India, known as an agricultural and commercial center in the Nimar region.
-
C.
Karmala
Karmala is a town in Maharashtra, India, known as a local administrative and commercial center within Solapur district.
-
D.
Bharuch
Bharuch is an ancient port city in the Indian state of Gujarat, historically significant as a major trading hub on the banks of the Narmada River.
-
E.
Jwalapur
Jwalapur is a prominent suburban town and commercial hub near Haridwar in the Indian state of Uttarakhand.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fa7c9ec81908c685612994543e3 |
completed | April 10, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f66854281c8190bd8d21d501cddb89 |
completed | May 2, 2026, 9:10 p.m. |
Created at: April 8, 2026, 9:54 p.m.