Triple
T8590343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Political and Security Committee |
E203412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Council preparatory body |
C655
|
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: Council preparatory body Context triple: [Political and Security Committee, instanceOf, Council preparatory body]
-
A.
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.
-
B.
advisory body
chosen
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
-
C.
provisional legislative body
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.
-
D.
municipal advisory committee
A municipal advisory committee is a formally appointed group of community members that provides recommendations and expert input to local government officials on specific policy areas, projects, or issues.
-
E.
municipal government committee
A municipal government committee is a formally organized group within a local government tasked with studying specific issues, advising the city or town council, and sometimes making decisions or recommendations on policies, services, and regulations affecting the community.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.