Triple
T13223075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kudal railway station |
E314803
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Kudal |
E314803
|
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: Kudal | Statement: [Kudal railway station, locatedIn, Kudal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kudal Context triple: [Kudal railway station, locatedIn, Kudal]
-
A.
Kudal
chosen
Kudal is a town in Maharashtra’s Sindhudurg district, known as a commercial and transport hub in the Konkan region.
-
B.
Kundalpur
Kundalpur is a historically significant Jain pilgrimage site in India, revered as the birthplace of Lord Mahavira.
-
C.
Kukanoor
Kukanoor is a historic village in Karnataka, India, known for its ancient temples and archaeological significance.
-
D.
Khandala
Khandala is a popular hill station in Maharashtra, India, known for its scenic valleys, waterfalls, and trekking spots in the Western Ghats.
-
E.
Narmadapuram
Narmadapuram is a city in the central Indian state of Madhya Pradesh, situated on the banks of the Narmada River and serving as an important regional administrative and cultural center.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf74d708190a61d8ad938653b06 |
completed | April 10, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff24be9881908b96f3e72325e55f |
completed | May 3, 2026, 7:54 a.m. |
Created at: April 9, 2026, 9:19 p.m.