Triple
T213230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament of Egypt |
E4761
|
entity |
| Predicate | re-establishedAsBicameral |
P1312
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Parliament of Egypt, re-establishedAsBicameral, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: re-establishedAsBicameral Context triple: [Parliament of Egypt, re-establishedAsBicameral, 2019]
-
A.
hasBicameralStructure
chosen
Indicates that an entity possesses a two-chamber (two-house) internal organizational or legislative structure.
-
B.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
-
C.
ratifiedOn
Indicates the date or point in time at which an agreement, treaty, or formal decision was officially approved and made valid.
-
D.
isBipartisan
Indicates that an action, decision, or stance is supported or undertaken by members of two (or more) opposing political parties.
-
E.
stateOfFirstRatification
Indicates the state in which an agreement, treaty, or document was first formally ratified.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c313d108190a65d3e939f961bef |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b509400819093a6c1a1bac861e3 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.