Triple
T20170612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Nimar |
E491947
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Harsud |
—
|
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: Harsud | Statement: [East Nimar, containsTown, Harsud]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Harsud Context triple: [East Nimar, containsTown, Harsud]
-
A.
Harsud
chosen
Harsud is a historic town in Madhya Pradesh, India, known for being submerged and relocated due to the construction of the Indira Sagar Dam on the Narmada River.
-
B.
Harsil
Harsil is a serene Himalayan village in Uttarakhand, India, known for its apple orchards, scenic river valley, and as a stopover on the route to the Gangotri temple.
-
C.
Bhilodi
Bhilodi is an alternative name for Bhili, an Indo-Aryan language spoken primarily by the Bhil people of western and central India.
-
D.
Harhas
Harhas is a minor biblical figure mentioned in genealogical records as an ancestor in the line of Shallum.
-
E.
Dudhrej
Dudhrej is a town in the Surendranagar district of Gujarat, India, known for its residential areas and proximity to the city of Surendranagar.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66847ed9481908e6b23b399fa7005 |
completed | April 20, 2026, 5:54 p.m. |
Created at: April 11, 2026, 11:35 p.m.