Triple
T8699239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN General Assembly resolution 52/160 |
E206483
|
entity |
| Predicate | adoptedByVoteType |
P24498
|
FINISHED |
| Object | without a vote |
—
|
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: without a vote | Statement: [UN General Assembly resolution 52/160, adoptedByVoteType, without a vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedByVoteType Context triple: [UN General Assembly resolution 52/160, adoptedByVoteType, without a vote]
-
A.
adoptedByConsensus
Indicates that a decision, action, or change was formally accepted through a consensus process among the relevant participants.
-
B.
voteType
chosen
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
C.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
-
D.
approvedByReferendum
Indicates that a decision, measure, or proposal has been formally accepted through a public referendum vote.
-
E.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58b1434081908f50480bfb6f9d90 |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.