Triple
T2013715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 83 |
E43745
|
entity |
| Predicate | votingResult |
P10095
|
FINISHED |
| Object | 7 votes in favour |
—
|
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: 7 votes in favour | Statement: [United Nations Security Council Resolution 83, votingResult, 7 votes in favour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingResult Context triple: [United Nations Security Council Resolution 83, votingResult, 7 votes in favour]
-
A.
voteResult
chosen
Indicates the outcome or decision produced by a voting process involving the related entities.
-
B.
presidentialVote
Indicates that an entity casts or records a vote in a presidential election for a particular candidate or option.
-
C.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
D.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
E.
votingOrder
Indicates the sequence or priority in which entities cast their votes or have their votes considered.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b42d508190bf2b63132bb2ad77 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.