Triple
T18838163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relief of Saugor |
E460718
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Saugor |
—
|
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: Saugor | Statement: [Relief of Saugor, location, Saugor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saugor Context triple: [Relief of Saugor, location, Saugor]
-
A.
Jagdishpur
Jagdishpur is a town in the Amethi district of Uttar Pradesh, India, known for its industrial area and historical significance in the region.
-
B.
Jagdishpur
Jagdishpur is a town in the Bhojpur district of Bihar, India, historically known as the ancestral estate of the 19th-century freedom fighter Kunwar Singh.
-
C.
Besnagar
Besnagar is the ancient name of the historic city of Vidisha in central India, known for its archaeological remains and significance in early Indian history.
-
D.
Verbania
Verbania is a lakeside city in northern Italy, situated on the shores of Lake Maggiore near the Swiss border.
-
E.
Sohagpur
chosen
Sohagpur is a town in the Narmadapuram district of Madhya Pradesh, India, known as a local commercial center and access point to nearby forested and wildlife areas.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99f443881909516a82208fd0178 |
completed | April 20, 2026, 4:20 a.m. |
Created at: April 10, 2026, 11:56 a.m.