Triple
T17033159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal Odisha |
E413249
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Gopalpur |
E1172075
|
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: Gopalpur | Statement: [Coastal Odisha, hasCity, Gopalpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gopalpur Context triple: [Coastal Odisha, hasCity, Gopalpur]
-
A.
Gopalpur-on-Sea
chosen
Gopalpur-on-Sea is a coastal town and popular beach destination on the Bay of Bengal in Odisha, India.
-
B.
Vikrampura
Vikrampura was an important historical city that served as a principal royal center of the medieval Indian Pala dynasty in eastern India.
-
C.
Puri
Puri is a coastal city in the Indian state of Odisha, renowned as a major Hindu pilgrimage site and home to the famous Jagannath Temple.
-
D.
Chandipur
Chandipur is a coastal town in Odisha, India, known for its unique beach where the sea recedes dramatically during low tide, exposing vast stretches of sand.
-
E.
Hirakud town
Hirakud town is a settlement in the Indian state of Odisha best known for its proximity to the major Hirakud Dam on the Mahanadi River.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8ed79448190a750a29a99913fda |
completed | April 18, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ed2ad708190a250762997611569 |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:33 a.m.