Triple
T7307776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telangana movement |
E168019
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Warangal |
E258043
|
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: Warangal | Statement: [Telangana movement, majorCity, Warangal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Warangal Context triple: [Telangana movement, majorCity, Warangal]
-
A.
Warangal
chosen
Warangal is a historic city in southern India known for its Kakatiya-era forts, temples, and monuments, and is one of the major urban centers of the state of Telangana.
-
B.
Bhadrachalam
Bhadrachalam is a temple town in Telangana, India, renowned for its major Sri Rama temple and its location along the banks of the Godavari River.
-
C.
Karimnagar
Karimnagar is a prominent city in the Indian state of Telangana, known as an important commercial and educational center in the region.
-
D.
Khammam
Khammam is a city in the Indian state of Telangana known for its historical forts, temples, and proximity to the Munneru River.
-
E.
Guntur
Guntur is a major city in the Indian state of Andhra Pradesh, known historically as an important administrative and commercial center in southeastern 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebd95bd48190865716e7565f45e6 |
completed | March 27, 2026, 8:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e56443b08190aee2c26633cdcbed |
completed | March 28, 2026, 2:27 p.m. |
Created at: March 27, 2026, 3:01 p.m.