Triple
T25822917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Member States of UNIDO |
E650447
|
entity |
| Predicate | collectivelyReview |
P90724
|
FINISHED |
| Object | UNIDO programme performance |
—
|
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: UNIDO programme performance | Statement: [Member States of UNIDO, collectivelyReview, UNIDO programme performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectivelyReview Context triple: [Member States of UNIDO, collectivelyReview, UNIDO programme performance]
-
A.
reviewAggregate
chosen
Indicates a summarized evaluation relationship where multiple individual reviews are combined into an overall rating or assessment for an entity.
-
B.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
C.
reviewedAs
Indicates that one entity has evaluated, critiqued, or assessed another entity in a particular capacity, role, or context.
-
D.
reviewedFor
Indicates that one entity has examined or evaluated another entity for a specific purpose, standard, or context.
-
E.
reviewableBy
Indicates that an entity is subject to evaluation, inspection, or assessment by a specified agent or party.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 22, 2026, 7:30 a.m.