Triple
T11323176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States of India |
E268141
|
entity |
| Predicate | haveLegislativeModel |
P15791
|
FINISHED |
| Object | unicameral or bicameral |
—
|
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: unicameral or bicameral | Statement: [States of India, haveLegislativeModel, unicameral or bicameral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveLegislativeModel Context triple: [States of India, haveLegislativeModel, unicameral or bicameral]
-
A.
hasLegislatureType
chosen
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
B.
hasLegislativeType
Indicates that something is associated with, classified by, or characterized as a particular type or category of legislation or legislative measure.
-
C.
legislativeBase
Indicates that one entity serves as the legal or legislative basis, authority, or foundation for another entity or action.
-
D.
hasAssociatedLegislature
Indicates that an entity is linked to a specific legislative body that holds authority or responsibility over it.
-
E.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e122e48190b3f890de8d561480 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.