Triple
T12757413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Malavelly |
E304895
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Malavalli |
E367806
|
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: Malavalli | Statement: [Battle of Malavelly, location, Malavalli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Malavalli Context triple: [Battle of Malavelly, location, Malavalli]
-
A.
Malavalli
chosen
Malavalli is a town in the Mandya district of Karnataka, India, known for its proximity to the Shimsha River and its agricultural surroundings.
-
B.
Kammala
Kammala was a historical figure known primarily as one of the children of Zhenjin, the Crown Prince of the Yuan dynasty and son of Kublai Khan.
-
C.
Maddur
Maddur is a town in Karnataka, India, known for its location between Bengaluru and Mysuru and its popular local snack, Maddur vada.
-
D.
Ukkadam
Ukkadam is a prominent commercial and transport hub in Coimbatore, Tamil Nadu, known for its busy markets and connectivity.
-
E.
Mavalli
Mavalli is a neighborhood in Bengaluru, India, known for its proximity to Lalbagh Botanical Garden and its mix of residential areas, local markets, and historic eateries.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8b57b88190b29b8fdca415c81c |
completed | April 10, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f67c9c93248190b77c7d229da64ffb |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 9, 2026, 5:27 p.m.