Triple
T9900917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devapala |
E182277
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Monghyr |
E190832
|
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: Monghyr | Statement: [Devapala, capital, Monghyr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Monghyr Context triple: [Devapala, capital, 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.
Samalkha
Samalkha is a town in the northern Indian state of Haryana, known for its industrial activity and location along major transport routes.
-
C.
Monyash
Monyash is a small historic village in the Derbyshire Peak District of England, known for its limestone scenery and proximity to popular walking areas.
-
D.
Muye
Muye was the site of an ancient Chinese battlefield where the Zhou forces decisively overthrew the Shang dynasty.
-
E.
Huwara
Huwara is a Palestinian town in the central West Bank, located south of Nablus along a major north–south roadway and often noted as a flashpoint in the Israeli–Palestinian conflict.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4e0705c8190bd17e36aff615cdd |
completed | April 2, 2026, 12:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1eb2125208190b4cf549d67d1ca42 |
completed | April 5, 2026, 4:54 a.m. |
Created at: March 30, 2026, 8:40 p.m.