Triple
T12370937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambay region of Gujarat |
E294998
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Cambay |
E626555
|
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: Cambay | Statement: [Cambay region of Gujarat, hasMajorCity, Cambay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cambay Context triple: [Cambay region of Gujarat, hasMajorCity, Cambay]
-
A.
Cambay
chosen
Cambay is a historic port city in western India that flourished as a major center of maritime trade and commerce in the Indian Ocean world.
-
B.
Naupada
Naupada is a prominent residential and commercial locality within the city of Thane in Maharashtra, India.
-
C.
Devgad
Devgad is a coastal town in Maharashtra, India, known for its historic sea fort and as a major center of Alphonso mango cultivation.
-
D.
Jambusar
Jambusar is a town in the Bharuch district of Gujarat, India, known for its historical significance and regional trade and agriculture.
-
E.
Navsari
Navsari is a city in the Indian state of Gujarat known historically as a center of Parsi culture and commerce.
- 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_69f62abfd9c081909803691d3fc4f149 |
completed | May 2, 2026, 4:48 p.m. |
Created at: April 8, 2026, 9:54 p.m.