Triple
T2028828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 85 |
E44469
|
entity |
| Predicate | againstVotes |
P5055
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [United Nations Security Council Resolution 85, againstVotes, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: againstVotes Context triple: [United Nations Security Council Resolution 85, againstVotes, 0]
-
A.
voteAgainst
chosen
Indicates that an entity formally expresses opposition to a proposal, decision, or candidate in a voting process.
-
B.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
C.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
D.
abstentions
Indicates that certain eligible participants chose not to cast a vote or express a position in a decision-making process.
-
E.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9136f888190b0fd03530e9eda1e |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.