Triple
T4420699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Country-Based Pooled Funds |
E95089
|
entity |
| Predicate | allocationDecidedBy |
P52403
|
FINISHED |
| Object | Humanitarian Coordinator |
—
|
LITERAL FINISHED |
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: Humanitarian Coordinator | Statement: [Country-Based Pooled Funds, allocationDecidedBy, Humanitarian Coordinator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocationDecidedBy Context triple: [Country-Based Pooled Funds, allocationDecidedBy, Humanitarian Coordinator]
-
A.
allottedBy
chosen
Indicates that something has been assigned, distributed, or allocated by a particular agent or authority.
-
B.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
-
C.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
D.
allocationAuthority
Indicates that an entity has the power or right to decide how resources, tasks, or responsibilities are distributed among others.
-
E.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35521e020819099e72b9e2ccbd36d |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.