Triple
T31006207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolesi Jirga |
E790071
|
entity |
| Predicate | bicameralLegislatureWith |
P9629
|
FINISHED |
| Object | Meshrano Jirga |
—
|
NE NERFINISHED |
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: Meshrano Jirga | Statement: [Wolesi Jirga, bicameralLegislatureWith, Meshrano Jirga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bicameralLegislatureWith Context triple: [Wolesi Jirga, bicameralLegislatureWith, Meshrano Jirga]
-
A.
hasBicameralStructure
Indicates that an entity possesses a two-chamber (two-house) internal organizational or legislative structure.
-
B.
isBicameralJointCommittee
Indicates that a committee is a joint body composed of members from both chambers of a bicameral legislature.
-
C.
hasPositionInBicameralSystem
Indicates that an entity holds a specific role or seat within one of the chambers of a bicameral legislative system.
-
D.
coLegislatureWith
chosen
Indicates that two legislative bodies share lawmaking authority within the same political system or jurisdiction.
-
E.
hasUnicameralOrBicameralContext
Indicates that an entity is associated with a legislative context specifying whether it is unicameral or bicameral.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:57 p.m.