Triple
T2770710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oil-for-Food Programme |
E61447
|
entity |
| Predicate | implementedInPhases |
P37745
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Oil-for-Food Programme, implementedInPhases, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedInPhases Context triple: [Oil-for-Food Programme, implementedInPhases, yes]
-
A.
builtInPhases
Indicates that something is constructed, developed, or implemented in distinct, sequential stages or phases.
-
B.
hasMultiplePhases
chosen
Indicates that the related process, event, or activity occurs in more than one distinct phase or stage.
-
C.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
D.
phasesOut
Indicates the process by which one entity or condition is gradually discontinued or removed in favor of another over time.
-
E.
implementedOn
Indicates that something (such as a feature, standard, or specification) is realized, executed, or put into effect within or on a particular platform, system, or environment.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.