Triple
T10691208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raichur Doab |
E252011
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Raichur |
E37145
|
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: Raichur | Statement: [Raichur Doab, containsCity, Raichur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raichur Context triple: [Raichur Doab, containsCity, Raichur]
-
A.
Raichur
chosen
Raichur is a historic city in the Indian state of Karnataka, known for its ancient forts, archaeological significance, and strategic location between major river systems.
-
B.
Yadgir
Yadgir is a district in the Indian state of Karnataka, known for its agricultural economy and historical forts and temples.
-
C.
Narsapur
Narsapur is a prominent town in Telangana, India, known as one of the major urban centers of Medak district.
-
D.
Nagole
Nagole is a residential and commercial neighborhood in Hyderabad, India, served as a key terminus and transit hub on the Hyderabad Metro network.
-
E.
Ulhasnagar
Ulhasnagar is a city in the Mumbai Metropolitan Region of Maharashtra, India, known for its large Sindhi community and extensive furniture and textile markets.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd3705788190bcbdef93b4c5f574 |
completed | April 9, 2026, 1:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de225f57948190aaf2954bce91f752 |
completed | April 14, 2026, 11:17 a.m. |
Created at: April 8, 2026, 9:11 p.m.