Triple
T18874953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 50 |
E461657
|
entity |
| Predicate | votingSummary |
P8455
|
FINISHED |
| Object | 8 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: 8 votes in favour | Statement: [United Nations Security Council Resolution 50, votingSummary, 8 votes in favour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingSummary Context triple: [United Nations Security Council Resolution 50, votingSummary, 8 votes in favour]
-
A.
voteResult
Indicates the outcome or decision produced by a voting process involving the related entities.
-
B.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
C.
totalVotesCast
chosen
Indicates the total number of votes that have been cast in a given election or voting event.
-
D.
ballotStatus
Indicates the current state or outcome of a ballot within a voting or decision-making process.
-
E.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3cd49748190948d535918aec3de |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.