Triple
T547949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legislative Assembly of Queensland |
E12772
|
entity |
| Predicate | isUnicameralSince |
P9596
|
FINISHED |
| Object | 1922 |
—
|
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: 1922 | Statement: [Legislative Assembly of Queensland, isUnicameralSince, 1922]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnicameralSince Context triple: [Legislative Assembly of Queensland, isUnicameralSince, 1922]
-
A.
isUnicameral
chosen
Indicates that a legislative body consists of a single chamber or house, rather than multiple separate chambers.
-
B.
hasBicameralStructure
Indicates that an entity possesses a two-chamber (two-house) internal organizational or legislative structure.
-
C.
hasPlenaryChamber
Indicates that an institution or governing body possesses a designated plenary chamber where all members can meet and deliberate together.
-
D.
isBicameralPartnerOf
Indicates that one legislative body or chamber forms one of the two cooperating parts of a bicameral partnership with another.
-
E.
currentRepresentativeChamber
Indicates that an entity currently serves as a representative in a specific legislative chamber.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498e2e8c88190a66d759ed3094e18 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.