Triple
T8225198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addis Ababa Action Agenda on financing for development |
E192157
|
entity |
| Predicate | followUpReportedIn |
P52538
|
FINISHED |
| Object | Inter-agency Task Force on Financing for Development reports |
—
|
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: Inter-agency Task Force on Financing for Development reports | Statement: [Addis Ababa Action Agenda on financing for development, followUpReportedIn, Inter-agency Task Force on Financing for Development reports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followUpReportedIn Context triple: [Addis Ababa Action Agenda on financing for development, followUpReportedIn, Inter-agency Task Force on Financing for Development reports]
-
A.
followsUp
Indicates that one entity continues, responds to, or builds upon a previous entity, typically as a subsequent action, communication, or step.
-
B.
mayReportTo
Indicates that one entity is permitted or allowed to have a reporting relationship to another entity, such as an employee being allowed to report to a particular manager.
-
C.
followUpMechanism
chosen
Indicates a mechanism or process that is used to continue, monitor, or respond to a prior action, event, or communication.
-
D.
followUpRelease
Indicates that one release occurs subsequently as a continuation or update to a previous release.
-
E.
scoreReportedTo
Indicates that a score or result has been communicated or submitted from one party to another.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb77cdcc248190bc6c5b0271da8a08 |
completed | March 31, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.