Triple
T4762479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharashtra Legislative Assembly |
E105728
|
entity |
| Predicate | isBicameralLegislatureComponent |
P46933
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Maharashtra Legislative Assembly, isBicameralLegislatureComponent, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBicameralLegislatureComponent Context triple: [Maharashtra Legislative Assembly, isBicameralLegislatureComponent, Yes]
-
A.
hasBicameralStructure
Indicates that an entity possesses a two-chamber (two-house) internal organizational or legislative structure.
-
B.
hasUnicameralOrBicameralContext
chosen
Indicates that an entity is associated with a legislative context specifying whether it is unicameral or bicameral.
-
C.
isUnicameral
Indicates that a legislative body consists of a single chamber or house, rather than multiple separate chambers.
-
D.
isBicameralPartnerOf
Indicates that one legislative body or chamber forms one of the two cooperating parts of a bicameral partnership with another.
-
E.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.