Triple
T151486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN General Assembly Resolution 68/262 |
E3439
|
entity |
| Predicate | abstentions |
P5056
|
FINISHED |
| Object | 58 |
—
|
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: 58 | Statement: [UN General Assembly Resolution 68/262, abstentions, 58]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abstentions Context triple: [UN General Assembly Resolution 68/262, abstentions, 58]
-
A.
elects
Indicates that one entity selects or chooses another entity for a position, role, or office, typically through a formal voting process.
-
B.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
-
C.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
D.
affirms
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
-
E.
excludes
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580f55a88190b37b54ee0ed5ac7c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256ea776081908fec36c3fdfb8d84 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.