Triple
T20431308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rights and freedoms working group |
E501137
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | body of the National Dialogue Conference |
C22782
|
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: body of the National Dialogue Conference Context triple: [rights and freedoms working group, instanceOf, body of the National Dialogue Conference]
-
A.
negotiation body
chosen
A negotiation body is an organized group or institution authorized to represent parties’ interests, conduct discussions, and reach agreements in formal negotiation processes.
-
B.
political dialogue
Political dialogue is the process of structured or informal communication among individuals, groups, or institutions to discuss, negotiate, and shape public policies, power relations, and collective decisions within a political context.
-
C.
United Nations outcome document
A United Nations outcome document is a formal, negotiated text adopted by UN member states that records agreed conclusions, commitments, and recommended actions resulting from a UN conference, summit, or meeting.
-
D.
Sudanese political agreement
A Sudanese political agreement is a formal accord between Sudanese political actors or factions that outlines shared principles, power arrangements, and mechanisms for governance, conflict resolution, or transition.
-
E.
diplomatic conference
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:31 a.m.