Triple
T25822893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Member States of UNIDO |
E650447
|
entity |
| Predicate | exercisePowerThrough |
P19487
|
FINISHED |
| Object | UNIDO General Conference |
—
|
NE NERFINISHED |
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 General Conference | Statement: [Member States of UNIDO, exercisePowerThrough, UNIDO General Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exercisePowerThrough Context triple: [Member States of UNIDO, exercisePowerThrough, UNIDO General Conference]
-
A.
strengthPeak
Indicates the point or period at which an entity’s strength reaches its maximum level.
-
B.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
C.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
D.
exercisesPowerInNameOf
Indicates that one entity wields authority or influence on behalf of, and under the authorization or representation of, another entity.
-
E.
exerciseOfPower
chosen
Indicates the exertion or application of authority, control, or influence by one entity over another or within a given 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 7:30 a.m.