Triple
T16625212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Union of Iraq |
E403926
|
entity |
| Predicate | parliamentarySystemRole |
P40745
|
FINISHED |
| Object | second 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: second chamber | Statement: [Council of Union of Iraq, parliamentarySystemRole, second chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentarySystemRole Context triple: [Council of Union of Iraq, parliamentarySystemRole, second chamber]
-
A.
parliamentaryRoleIn
chosen
Indicates that an entity holds or has held a specific role, position, or function within a particular parliament or parliamentary body.
-
B.
legislativeRole
Indicates that an entity holds or performs a specific official position, function, or duty within a legislative body or lawmaking process.
-
C.
partySystemRole
Indicates the specific functional role or capacity that a party assumes within a given system or context.
-
D.
ParliamentarianSide
Indicates that one entity is aligned with, represents, or belongs to the Parliamentarian side in a political or legislative context.
-
E.
roleInCongress
Indicates the specific position or function an individual holds within a legislative congress.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37551cd888190becc21deba87980d |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.