Triple
T30914895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Béla Kun |
E787550
|
entity |
| Predicate | afterReleaseFromPOW |
P174738
|
FINISHED |
| Object | joined Bolsheviks in Petrograd |
—
|
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: joined Bolsheviks in Petrograd | Statement: [Béla Kun, afterReleaseFromPOW, joined Bolsheviks in Petrograd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterReleaseFromPOW Context triple: [Béla Kun, afterReleaseFromPOW, joined Bolsheviks in Petrograd]
-
A.
afterRelease
Indicates that one event, action, or state occurs subsequent to the release of another entity or condition.
-
B.
hasPOW
Indicates that one entity holds another entity as a prisoner of war.
-
C.
releasedAfterSuccessOf
Indicates that one entity was released following, and likely in response to, the successful performance or reception of another entity.
-
D.
laterProofBy
Indicates that one proof is derived or established after, and possibly building upon, an earlier proof.
-
E.
continuedAsAccountingUnitAfterCoinWithdrawal
Indicates that an entity remained in use as an accounting or value-tracking unit even after its associated physical coins were withdrawn from circulation.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 29, 2026, 8:51 p.m.