Triple
T31831883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cortes of Portugal |
E812559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical representative assembly |
C59797
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical representative assembly Context triple: [Cortes of Portugal, instanceOf, historical representative assembly]
-
A.
historical assembly
chosen
A historical assembly is a formally organized gathering of people in the past, convened at a specific time and place to deliberate, decide, or legislate on matters of public, political, or social importance.
-
B.
deliberative assembly
A deliberative assembly is a group of people who meet to discuss, debate, and decide on matters of common concern, typically following formal rules of procedure.
-
C.
revolutionary parliament
A revolutionary parliament is a legislative body formed during or after a revolution to represent the new political order, draft foundational laws or constitutions, and legitimize transformative changes in governance.
-
D.
colonial diplomatic assembly
A colonial diplomatic assembly is a formal gathering of representatives from colonial powers and/or their territories convened to negotiate treaties, coordinate policies, and manage political, economic, or territorial relations within an imperial or colonial context.
-
E.
revolutionary congress
A revolutionary congress is a formal assembly of representatives convened to lead, coordinate, and legitimize a political or social revolution, often drafting new governing frameworks and strategies for transformative change.
- F. None of above.
Provenance (1 batch)
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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:47 p.m.