Triple
T25945982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union of Bessarabia with Romania |
E653838
|
entity |
| Predicate | voteAbstentions |
P5056
|
FINISHED |
| Object | 36 deputies |
—
|
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: 36 deputies | Statement: [Union of Bessarabia with Romania, voteAbstentions, 36 deputies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteAbstentions Context triple: [Union of Bessarabia with Romania, voteAbstentions, 36 deputies]
-
A.
abstentions
chosen
Indicates that certain eligible participants chose not to cast a vote or express a position in a decision-making process.
-
B.
committedAbstentionFrom
Indicates that an entity has formally pledged or undertaken a deliberate abstention from performing a particular action or engaging in a specified activity.
-
C.
requiresAbstentionFrom
Indicates that one entity imposes or necessitates refraining from a specific action, behavior, or substance by another entity.
-
D.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
-
E.
voteAgainst
Indicates that an entity formally expresses opposition to a proposal, decision, or candidate in a voting process.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60464d4988190bc39b78c8e418547 |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:43 a.m.