Triple
T4685533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Char Dham |
E103911
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Puri |
E415657
|
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: Puri | Statement: [Char Dham, hasPart, Puri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Puri Context triple: [Char Dham, hasPart, Puri]
-
A.
Vikrampura
Vikrampura was an important historical city that served as a principal royal center of the medieval Indian Pala dynasty in eastern India.
-
B.
Mandapam
Mandapam is a coastal town in Tamil Nadu, India, known as a gateway to Rameswaram and for its fishing and marine activities.
-
C.
Pavapuri
Pavapuri is a revered Jain pilgrimage site in Bihar, India, best known as the place where Mahavira, the 24th Tirthankara, attained nirvana.
-
D.
Amarkantak town
Amarkantak town is a small pilgrimage and tourist town in Madhya Pradesh, India, revered as the source region of several major rivers and home to numerous Hindu temples and ashrams.
-
E.
Puri district
chosen
Puri district is a coastal district in the Indian state of Odisha, renowned for the temple town of Puri and its cultural and religious significance.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6383c83881908a978e471fe422a2 |
completed | March 20, 2026, 3:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be4399ded08190ba97c9c2f98395ec |
completed | March 21, 2026, 7:07 a.m. |
Created at: March 20, 2026, 1:16 p.m.