Triple
T19671016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFAD Evaluation Policy |
E472333
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational policy document |
C9168
|
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 policy document Context triple: [IFAD Evaluation Policy, instanceOf, organizational policy document]
-
A.
organizational policy
chosen
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.
-
B.
public policy document
A public policy document is an official written statement issued by a government or public institution that outlines decisions, rules, or strategies intended to address societal issues and guide future actions.
-
C.
financial policy document
A financial policy document is an official written guideline that defines an organization’s principles, rules, and procedures for managing, controlling, and reporting its financial activities.
-
D.
public policy office
A public policy office is an organizational unit within a government or institution responsible for researching, developing, analyzing, and coordinating policies to address public issues and guide decision-making.
-
E.
regulatory document
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:45 p.m.