Triple
T355835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council |
E7539
|
entity |
| Predicate | chairingSystem |
P11659
|
FINISHED |
| Object | rotating presidency |
—
|
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: rotating presidency | Statement: [United Nations Security Council, chairingSystem, rotating presidency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chairingSystem Context triple: [United Nations Security Council, chairingSystem, rotating presidency]
-
A.
chairperson
Indicates that one entity serves as the leader or head of a group, committee, or organization in relation to another entity.
-
B.
committeeFunction
Indicates that a committee performs, is responsible for, or is associated with a particular function or role.
-
C.
committeeMember
Indicates that an entity serves as a member of a particular committee.
-
D.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
E.
boardMember
Indicates that a person serves on the governing board of an organization, participating in its oversight and decision-making.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebad8bf08190b4a38ffd9157d641 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9589e7c8190b2d3af8f858c96af |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0b23ec8190bef9d593162388a4 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.