Triple
T4910973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwarka |
E110229
|
entity |
| Predicate | nearbySite |
P350
|
FINISHED |
| Object | Bet Dwarka |
E363383
|
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: Bet Dwarka | Statement: [Dwarka, nearbySite, Bet Dwarka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bet Dwarka Context triple: [Dwarka, nearbySite, Bet Dwarka]
-
A.
Bet Dwarka
chosen
Bet Dwarka is a small island off the coast of Gujarat, India, revered in Hindu tradition as a legendary residence of Lord Krishna and an important pilgrimage site.
-
B.
Dvaraka
Dvaraka is an ancient and sacred coastal city in western India, revered in Hindu tradition as the legendary kingdom of Lord Krishna.
-
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.
Surendranagar
Surendranagar is a city in the Indian state of Gujarat known historically as a regional trade and administrative center.
-
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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9acc0c819080b07e2e7924d163 |
completed | March 20, 2026, 3:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be92394f048190b6c0c87eea844f56 |
completed | March 21, 2026, 12:42 p.m. |
Created at: March 20, 2026, 1:29 p.m.