Triple
T826913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tynwald |
E17873
|
entity |
| Predicate | lowerHouseRole |
P11042
|
FINISHED |
| Object | directly elected chamber |
—
|
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: directly elected chamber | Statement: [Tynwald, lowerHouseRole, directly elected chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerHouseRole Context triple: [Tynwald, lowerHouseRole, directly elected chamber]
-
A.
lowerHouse
Indicates that one entity functions as the lower chamber of a bicameral legislature in relation to a given political body or system.
-
B.
legislativeRole
Indicates that an entity holds or performs a specific official position, function, or duty within a legislative body or lawmaking process.
-
C.
roleInCongress
Indicates the specific position or function an individual holds within a legislative congress.
-
D.
relationToLowerHouse
chosen
Indicates the type or nature of a subject’s formal relationship to a lower house within a bicameral legislative or parliamentary system.
-
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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab989748819091a3809a747a1c5b |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa781e1081909df006f730296c53 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.