Triple
T36382606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warangal West |
E896086
|
entity |
| Predicate | constituencyNumberInTelangana |
P195616
|
FINISHED |
| Object | 2 |
—
|
LITERAL 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: 2 | Statement: [Warangal West, constituencyNumberInTelangana, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constituencyNumberInTelangana Context triple: [Warangal West, constituencyNumberInTelangana, 2]
-
A.
constituencyNumberInJharkhand
Indicates the numerical identifier assigned to a specific electoral constituency within the state of Jharkhand.
-
B.
assemblyConstituencyNumberInUttarPradesh
Indicates the specific numerical identifier assigned to an assembly constituency within the state of Uttar Pradesh.
-
C.
unionTerritoryConstituency
Indicates a relationship where a parliamentary or legislative constituency is located within, or designated as part of, a specific union territory.
-
D.
constituencyNumberInBihar
Indicates the numerical identifier assigned to a specific electoral constituency within the state of Bihar.
-
E.
isLokSabhaConstituency
Indicates that an entity functions as a Lok Sabha (lower house of India's Parliament) electoral constituency.
- F. None of above. chosen
Provenance (4 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69fddac42c4081908568649058e86458 |
completed | May 8, 2026, 12:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.