Triple
T17350876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cham |
E421806
|
entity |
| Predicate | historicalCapital |
P2536
|
FINISHED |
| Object | Indrapura |
E356725
|
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: Indrapura | Statement: [Cham, historicalCapital, Indrapura]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Indrapura Context triple: [Cham, historicalCapital, Indrapura]
-
A.
Indrapura
chosen
Indrapura was a prominent historical capital city of the Champa kingdom in what is now central Vietnam.
-
B.
Vikrampura
Vikrampura was an important historical city that served as a principal royal center of the medieval Indian Pala dynasty in eastern India.
-
C.
Inderpuri
Inderpuri is a residential neighborhood in West Delhi, India, known for its proximity to the Pusa Institute and other central parts of New Delhi.
-
D.
Bhagwanpura
Bhagwanpura is a town in the Khargone district of Madhya Pradesh, India, known primarily as a local administrative and market center for surrounding rural areas.
-
E.
Jwalapur
Jwalapur is a prominent suburban town and commercial hub near Haridwar in the Indian state of Uttarakhand.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2ca0708190aae8306ec3a6f2a7 |
completed | April 19, 2026, 2:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0195585e5881909b0ad386b65112ba |
completed | May 11, 2026, 8:37 a.m. |
Created at: April 10, 2026, 5:44 a.m.