Triple
T28222917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pre-autonomous Galician Assembly |
E711508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provisional representative body |
C2331
|
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: provisional representative body Context triple: [pre-autonomous Galician Assembly, instanceOf, provisional representative body]
-
A.
provisional legislative body
chosen
A provisional legislative body is a temporary lawmaking assembly established to exercise legislative authority during a transitional or interim period before a permanent government structure is formed or restored.
-
B.
passenger representative body
A passenger representative body is an organized group or committee that advocates for the interests, rights, and needs of passengers in relation to transport providers and regulators.
-
C.
proposed governmental body
A proposed governmental body is a conceptual organization suggested to perform specific public functions or governance roles, but which has not yet been formally established or granted legal authority.
-
D.
ad hoc governmental body
An ad hoc governmental body is a temporary, specially formed public entity created by a government to address a specific issue, task, or crisis and dissolved once its purpose is fulfilled.
-
E.
auxiliary body of a committee of permanent representatives
An auxiliary body of a committee of permanent representatives is a subordinate group established to support, advise, or carry out specific preparatory or technical tasks on behalf of the main committee of permanent representatives.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:47 p.m.