Triple
T33862864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Executive Committee of the Multilateral Fund |
E867967
|
entity |
| Predicate | usesImplementingAgencies |
P109273
|
FINISHED |
| Object | UNEP |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: UNEP | Statement: [Executive Committee of the Multilateral Fund, usesImplementingAgencies, UNEP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesImplementingAgencies Context triple: [Executive Committee of the Multilateral Fund, usesImplementingAgencies, UNEP]
-
A.
implementedByAgency
Indicates that an action, program, or policy is carried out or executed by a specific agency.
-
B.
mainImplementingAgency
chosen
Indicates which agency has primary responsibility for implementing a given project, program, or policy.
-
C.
collaboratingAgencies
Indicates that multiple agencies are working together in a coordinated manner toward shared goals or activities.
-
D.
headquartersOfImplementingAgency
Indicates that a specified location serves as the main headquarters of the agency responsible for implementing a particular project, program, or policy.
-
E.
usedByAgency
Indicates that something (such as a resource, tool, or service) is utilized or employed by an agency.
- F. None of above.
Provenance (3 batches)
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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:47 a.m.