Triple
T4518316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Constitutional Era |
E103205
|
entity |
| Predicate | parliamentType |
P6051
|
FINISHED |
| Object | bicameral legislature |
—
|
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: bicameral legislature | Statement: [Second Constitutional Era, parliamentType, bicameral legislature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentType Context triple: [Second Constitutional Era, parliamentType, bicameral legislature]
-
A.
parliamentaryGroupType
Indicates the specific kind or category of parliamentary group to which an entity belongs.
-
B.
typeOfParliamentaryBody
chosen
Indicates the specific kind or classification of a parliamentary body that an entity represents (e.g., lower house, upper house, unicameral chamber).
-
C.
parliamentaryHouse
Indicates that one entity functions as a parliamentary chamber or house within the legislative system of another entity.
-
D.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
E.
parliamentName
Indicates the official name assigned to a particular parliament.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd57465a10819086866e29f7a6eb02 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.