Triple
T22073770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pala period |
E545473
|
entity |
| Predicate | hasCapital |
P204
|
FINISHED |
| Object | Monghyr |
—
|
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: Monghyr | Statement: [Pala period, hasCapital, Monghyr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Monghyr Context triple: [Pala period, hasCapital, Monghyr]
-
A.
Monghyr
chosen
Monghyr (now usually spelled Munger) is a historic city in the Indian state of Bihar, known for its strategic location on the Ganges and its significance in various ancient and medieval Indian kingdoms.
-
B.
Mongyai
Mongyai is a town in Myanmar’s Shan State historically associated with the rulers of the former South Hsenwi principality.
-
C.
Khorlim
Khorlim is a village located in the North Goa district of the Indian state of Goa.
-
D.
Mohnyin
Mohnyin is a town in northern Myanmar that serves as an important local center within Kachin State.
-
E.
Huria
Huria is a marae-based Māori community associated with the Ngāti Ranginui iwi in Aotearoa New Zealand.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1288affb081908b64742f7bf467fa |
completed | April 28, 2026, 9:37 p.m. |
Created at: April 16, 2026, 8:28 p.m.