Triple
T20751848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavanasura |
E510740
|
entity |
| Predicate | killedAt |
P21754
|
FINISHED |
| Object | Madhupuri |
—
|
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: Madhupuri | Statement: [Lavanasura, killedAt, Madhupuri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Madhupuri Context triple: [Lavanasura, killedAt, Madhupuri]
-
A.
Madhupuri
chosen
Madhupuri is the mythical city associated with the demon king Lavanasura in Hindu epic tradition.
-
B.
Brajarajnagar
Brajarajnagar is a town in the Jharsuguda district of Odisha, India, known historically for its paper and industrial enterprises.
-
C.
Burhanpur
Burhanpur is a historic city in central India known for its Mughal-era architecture and strategic location on the banks of the Tapti River.
-
D.
Samastipur
Samastipur is a city in the Indian state of Bihar known as an important railway junction and agricultural trade center in the region.
-
E.
Rampurhat
Rampurhat is a town and important railway junction in the Birbhum district of West Bengal, India.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c22ad0c8819087a8db2bac8dd408 |
completed | April 21, 2026, 12:17 a.m. |
Created at: April 16, 2026, 12:34 p.m.