Triple
T14810675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GECF Statute |
E348169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational charter |
C7407
|
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: organizational charter Context triple: [GECF Statute, instanceOf, organizational charter]
-
A.
intergovernmental organization charter
An intergovernmental organization charter is a formal foundational treaty or document agreed upon by multiple sovereign states that establishes an international organization’s legal status, purposes, structures, and rules of operation.
-
B.
organizational bylaws
Organizational bylaws are the formal written rules that define an organization’s structure, governance procedures, member rights and responsibilities, and decision-making processes.
-
C.
colonial governing charter
A colonial governing charter is a formal legal document issued by a sovereign power that establishes the framework, authority, and rules by which a colony is organized and governed.
-
D.
organizational policy
An organizational policy is a formal, guiding principle or rule established by an organization to direct decisions, behaviors, and procedures in alignment with its goals, values, and legal obligations.
-
E.
constituent instrument of an international organization body
chosen
A constituent instrument of an international organization body is the foundational legal document or set of documents that establishes the body’s existence, defines its purposes, powers, structure, and procedures, and governs its functioning within the organization’s overall framework.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:46 a.m.