Triple
T19817441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharashtra Legislature |
E476094
|
entity |
| Predicate | hasLegislativeAssemblyStrength |
P11035
|
FINISHED |
| Object | 288 |
—
|
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: 288 | Statement: [Maharashtra Legislature, hasLegislativeAssemblyStrength, 288]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegislativeAssemblyStrength Context triple: [Maharashtra Legislature, hasLegislativeAssemblyStrength, 288]
-
A.
haveLegislativeAssemblyIn
Indicates that an entity possesses or is associated with a legislative assembly located in a specified place.
-
B.
ParliamentarianForceStrength
Indicates the magnitude or level of military or coercive power held or deployed by a parliamentary or legislature-aligned force in a given context.
-
C.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
D.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
E.
legislativeAssemblySeats
chosen
Indicates the number of seats an entity holds or is allocated in a legislative assembly.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fac7b481909a19ae0d608e01d9 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.