Triple
T32108457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algapur Assembly constituency |
E820049
|
entity |
| Predicate | lowerHouseOfState |
P241
|
FINISHED |
| Object | Assam Vidhan Sabha |
—
|
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: Assam Vidhan Sabha | Statement: [Algapur Assembly constituency, lowerHouseOfState, Assam Vidhan Sabha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerHouseOfState Context triple: [Algapur Assembly constituency, lowerHouseOfState, Assam Vidhan Sabha]
-
A.
lowerHouseOf
Indicates that one entity is the lower chamber in the bicameral legislature of another governing body or jurisdiction.
-
B.
lowerHouse
chosen
Indicates that one entity functions as the lower chamber of a bicameral legislature in relation to a given political body or system.
-
C.
lowerHouseSeat
Indicates that an entity holds or is associated with a seat in the lower house of a bicameral legislature.
-
D.
upperHouse
Indicates that one entity functions as the higher or upper legislative chamber in relation to a given political or governmental system.
-
E.
chamberOfCongress
Indicates that a legislative chamber is a constituent part or house of a specific congress or legislative body.
- F. None of above.
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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b69dd5ac8190b7431a060e482f5f |
completed | May 3, 2026, 2:44 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:27 a.m.