Triple
T19789902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pachmarhi |
E475381
|
entity |
| Predicate | hasNearbyCity |
P350
|
FINISHED |
| Object | Pipariya |
—
|
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: Pipariya | Statement: [Pachmarhi, hasNearbyCity, Pipariya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pipariya Context triple: [Pachmarhi, hasNearbyCity, Pipariya]
-
A.
Pipariya
chosen
Pipariya is a town in the Indian state of Madhya Pradesh, known as a key rail and road gateway to the nearby hill station of Pachmarhi.
-
B.
Pachhad
Pachhad is a legislative assembly constituency in the Sirmour district of Himachal Pradesh, India, represented in the state's Vidhan Sabha.
-
C.
Pipra
Pipra is a genus of small, brightly colored Neotropical manakins known for the males’ elaborate courtship displays in forest understories.
-
D.
Pirojpura
Pirojpura is a village located in the Patan district of the Indian state of Gujarat.
-
E.
Pupri
Pupri is a small town in the Sitamarhi district of the Indian state of Bihar, known primarily as a local commercial and administrative center for surrounding rural 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538ae5108190b80eb7de6f445f02 |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:49 p.m.