Triple
T18348002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Vishnuvardhana |
E439592
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Halebidu |
—
|
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: Halebidu | Statement: [King Vishnuvardhana, capital, Halebidu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Halebidu Context triple: [King Vishnuvardhana, capital, Halebidu]
-
A.
Belur
Belur is a locality in the Howrah district of West Bengal, India, known for its proximity to the Hooghly River and the famous Belur Math.
-
B.
Belur
chosen
Belur is a historic town in Karnataka, India, renowned for its exquisite Hoysala-era temple architecture, especially the Chennakeshava Temple.
-
C.
Hampi
Hampi is an ancient ruined city in Karnataka, India, famed for its monumental Hindu temples and as the former capital of the Vijayanagara Empire.
-
D.
Vimanapura
Vimanapura is a residential and institutional neighborhood in eastern Bengaluru, India, known for its proximity to the old HAL Airport and several aerospace and defense establishments.
-
E.
Badami
Badami is a historic town in Karnataka, India, renowned for its rock-cut cave temples and ancient Chalukyan architecture.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e514f594f88190a683e6224e091593 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 10:37 a.m.