Triple
T22376404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganjam district |
E553160
|
entity |
| Predicate | hasTouristAttraction |
P530
|
FINISHED |
| Object | Gopalpur-on-Sea |
—
|
NE NERFINISHED |
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-on-Sea | Statement: [Ganjam district, hasTouristAttraction, Gopalpur-on-Sea]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gopalpur-on-Sea Context triple: [Ganjam district, hasTouristAttraction, Gopalpur-on-Sea]
-
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.
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.
-
C.
Puri Beach
Puri Beach is a popular seaside destination on the Bay of Bengal in Puri, India, known for its religious significance, golden sands, and vibrant coastal culture.
-
D.
Puri
Puri is a common Indian surname associated with Punjabi Khatri and Sikh communities, often linked to North India.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158285d208190bc7d05d315267995 |
completed | April 29, 2026, 1 a.m. |
Created at: April 16, 2026, 8:45 p.m.