Triple
T7872887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellary Fort |
E182780
|
entity |
| Predicate | locatedIn |
P40
|
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 Fort, locatedIn, Ballari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ballari Context triple: [Bellary Fort, locatedIn, 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.
Satala
Satala is a coastal village and harbor area on the island of Tutuila in American Samoa, known historically as a commercial and maritime hub near the capital region.
-
D.
Malavalli
Malavalli is a town in the Mandya district of Karnataka, India, known for its proximity to the Shimsha River and its agricultural surroundings.
-
E.
Tosali
Tosali was an ancient city that served as a major political and administrative center of the Kalinga kingdom in eastern India.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39a6d93881908d68386e49bea1e3 |
completed | March 31, 2026, 3:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc93556f0c8190b072c3ec4c8e93bd |
completed | April 1, 2026, 3:39 a.m. |
Created at: March 30, 2026, 4:56 p.m.