Triple
T1712260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTI Bylaws |
E37208
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate bylaws |
C4382
|
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: corporate bylaws Context triple: [PTI Bylaws, instanceOf, corporate bylaws]
-
A.
organizational bylaws
chosen
Organizational bylaws are the formal written rules that define an organization’s structure, governance procedures, member rights and responsibilities, and decision-making processes.
-
B.
corporate governance law
Corporate governance law is the body of legal rules and principles that regulates how corporations are directed and controlled, defining the rights, responsibilities, and accountability mechanisms among shareholders, boards of directors, management, and other stakeholders.
-
C.
constituent instrument of an international organization body
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.
-
D.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
E.
board of trustees
A board of trustees is a governing body of individuals legally entrusted with overseeing an organization’s mission, assets, and strategic direction on behalf of its stakeholders or beneficiaries.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.