Triple
T28226293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1920 Tours Congress |
E711596
|
entity |
| Predicate | voteOn |
P164140
|
FINISHED |
| Object | adhesion to the Communist International |
—
|
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: adhesion to the Communist International | Statement: [1920 Tours Congress, voteOn, adhesion to the Communist International]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteOn Context triple: [1920 Tours Congress, voteOn, adhesion to the Communist International]
-
A.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
B.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
C.
vote
Indicates that an entity formally expresses a choice or preference in a decision-making process, typically an election or poll.
-
D.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
-
E.
voted
Indicates that an entity formally expressed a choice or decision, typically in an election, poll, or decision-making process, regarding another entity or option.
- F. None of above. chosen
Provenance (4 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64384644c81909b429ac2a5c34999 |
completed | May 2, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:50 p.m.