Triple
T14441050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache Incubator |
E358082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governance program |
C34761
|
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: governance program Context triple: [Apache Incubator, instanceOf, governance program]
-
A.
governance tool
A governance tool is a system or platform that helps organizations define, implement, monitor, and enforce policies, decision-making processes, and accountability structures to ensure compliant and effective management.
-
B.
governance doctrine
A governance doctrine is a coherent set of principles, rules, and practices that defines how authority is structured, decisions are made, and accountability is maintained within an organization or political system.
-
C.
governance position
A governance position is a formal role within an organization or institution responsible for overseeing decision-making, setting policies, and ensuring accountability and compliance with established rules and objectives.
-
D.
government regulatory program
A government regulatory program is an organized set of rules, procedures, and enforcement mechanisms established by a public authority to oversee, control, or guide specific activities or sectors in order to achieve defined policy objectives and protect the public interest.
-
E.
e-government program
An e-government program is an organized initiative that uses digital technologies to deliver public services, enhance government operations, and improve interaction between government, citizens, and businesses.
- F. None of above. chosen
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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:18 a.m.