Triple
T9334623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO field offices |
E224612
|
entity |
| Predicate | implementsProgramme |
P24641
|
FINISHED |
| Object | Education for All related initiatives |
—
|
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: Education for All related initiatives | Statement: [UNESCO field offices, implementsProgramme, Education for All related initiatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementsProgramme Context triple: [UNESCO field offices, implementsProgramme, Education for All related initiatives]
-
A.
implementsProgram
chosen
Indicates that an entity carries out, executes, or puts into effect a specified program or plan.
-
B.
hasProgramme
Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
-
C.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
D.
programmeName
Indicates that an entity has or is identified by a specific programme’s name.
-
E.
madeProgram
Indicates that one entity created, developed, or authored a program (such as software or a coded application).
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37ee53988190bcc76588edbc2858 |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.