Triple
T876077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNDG |
E18920
|
entity |
| Predicate | chairHeldBy |
P20987
|
FINISHED |
| Object | Administrator of the United Nations Development Programme |
—
|
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: Administrator of the United Nations Development Programme | Statement: [UNDG, chairHeldBy, Administrator of the United Nations Development Programme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chairHeldBy Context triple: [UNDG, chairHeldBy, Administrator of the United Nations Development Programme]
-
A.
canChair
Indicates that an entity has the authority or capability to preside over, lead, or chair a meeting, committee, or similar group.
-
B.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
C.
chairType
Indicates the specific kind or category of chair that an entity is classified as.
-
D.
chairSelectedFrom
Indicates that a particular chair has been chosen from a larger set or collection of chairs.
-
E.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
- F. None of above. chosen
Provenance (4 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acaf30a48190a10ed7fee464c444 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:39 p.m.