Triple
T11321549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raigad district |
E268104
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Alibag |
E704186
|
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: Alibag | Statement: [Raigad district, contains, Alibag]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alibag Context triple: [Raigad district, contains, Alibag]
-
A.
Alibag
chosen
Alibag is a coastal town in Maharashtra, India, known for its beaches, historic forts, and role as a popular weekend getaway from Mumbai.
-
B.
Dalgaon
Dalgaon is a town and administrative center located in the Darrang district of the northeastern Indian state of Assam.
-
C.
Tarapur
Tarapur is a town in the Anand district of Gujarat, India, known as a local commercial and agricultural center.
-
D.
Ratnagiri
Ratnagiri is a coastal city in Maharashtra, India, known for its Alphonso mangoes, historic forts, and scenic beaches along the Konkan coast.
-
E.
Karwar
Karwar is a coastal city in the Indian state of Karnataka, known for its beaches, port, and role as a key urban center in the Konkan region.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9dff37081909622623e66e17ccd |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e543055b588190a417b3d50ade989a |
completed | April 19, 2026, 9:03 p.m. |
Created at: April 8, 2026, 9:32 p.m.