Triple
T27752347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telangana Legislature |
E701243
|
entity |
| Predicate | hasChairmanIn |
P177308
|
FINISHED |
| Object | Telangana Legislative Council |
—
|
NE NERFINISHED |
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: Telangana Legislative Council | Statement: [Telangana Legislature, hasChairmanIn, Telangana Legislative Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChairmanIn Context triple: [Telangana Legislature, hasChairmanIn, Telangana Legislative Council]
-
A.
hasChairHolder
Indicates that an entity holds or occupies a specific chair position or role associated with another entity.
-
B.
hasChairmanTitle
Indicates that an entity holds the position or official title of chairman in relation to another entity or organization.
-
C.
hasChairpersonOrgan
Indicates that an organization or body has a specific organ (such as a board or committee) that holds the role of chairperson.
-
D.
coChairpersonOf
Indicates that a person serves jointly with one or more others as the chairperson of a group, organization, or committee.
-
E.
hasBoardChairperson
Indicates that an entity has a specific person serving as the chairperson of its board.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 27, 2026, 4:21 p.m.