Triple
T33238671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Representatives (New Zealand) |
E850903
|
entity |
| Predicate | becameUnicameral |
P57484
|
FINISHED |
| Object | 1951 |
—
|
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: 1951 | Statement: [House of Representatives (New Zealand), becameUnicameral, 1951]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameUnicameral Context triple: [House of Representatives (New Zealand), becameUnicameral, 1951]
-
A.
reorganizedAsUnicameralIn
chosen
Indicates that a previously different legislative structure was changed into a unicameral (single-chamber) system in a specified place or time.
-
B.
isUnicameral
Indicates that a legislative body consists of a single chamber or house, rather than multiple separate chambers.
-
C.
isUnicameralComponentOf
Indicates that a legislative body or chamber is a single-chamber (unicameral) part of a larger political or governmental system.
-
D.
changedLegislatureStructureTo
Indicates that an entity altered the organizational structure or composition of a legislative body to a new specified form.
-
E.
establishedAsHouseOfAssembly
Indicates that an entity was formally created or designated to function as a House of 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:31 a.m.