Triple
T15739168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSCE Committee of Senior Officials |
E381556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CSCE body |
C32781
|
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: CSCE body Context triple: [CSCE Committee of Senior Officials, instanceOf, CSCE body]
-
A.
CSCE institution
chosen
A CSCE institution is an organization or entity that participates in, supports, or is governed by the processes, principles, and agreements of the Conference on Security and Co-operation in Europe (now OSCE), focusing on security, cooperation, and human rights in the European region.
-
B.
CSCE document
A CSCE document is an official record used in construction projects to capture, communicate, and track changes, clarifications, or supplemental instructions related to the scope, cost, or execution of the work.
-
C.
collegiate body
A collegiate body is a formal group of individuals who collectively deliberate, decide, or govern on matters within a shared institutional or organizational authority.
-
D.
secretariat-type body
A secretariat-type body is an administrative organization that provides ongoing coordination, support, and implementation services for a larger governing or decision-making entity.
-
E.
university governing body
A university governing body is a formal group of appointed or elected individuals responsible for setting the institution’s strategic direction, overseeing its policies and finances, and ensuring accountability and compliance with legal and educational standards.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.