Triple
T1615488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellary |
E34707
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | Ballari |
E169792
|
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: Ballari | Statement: [Bellary, formerName, Ballari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ballari Context triple: [Bellary, formerName, Ballari]
-
A.
Ballari
chosen
Ballari is a major city in the Indian state of Karnataka, known for its rich mineral resources and historical forts.
-
B.
Ballana
Ballana is an important archaeological site in Lower Nubia known for its rich group of royal tumulus graves from the post-Meroitic period.
-
C.
Solan
Solan is a town in the Indian state of Himachal Pradesh known for its mushroom cultivation and as a growing commercial and educational hub in the region.
-
D.
Verbania
Verbania is a lakeside city in northern Italy, situated on the shores of Lake Maggiore near the Swiss border.
-
E.
Quarracino
Quarracino is an Italian-origin surname most notably associated with Argentine Cardinal Antonio Quarracino.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9099049e0819099763ecb09fb4f57 |
completed | March 5, 2026, 4:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad51cd2e54819086924378792eb2e3 |
completed | March 8, 2026, 10:39 a.m. |
Created at: March 4, 2026, 7:28 p.m.