Triple
T33332592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet economy |
E853446
|
entity |
| Predicate | bankingSystem |
P141209
|
FINISHED |
| Object | Gosbank monopoly |
—
|
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: Gosbank monopoly | Statement: [Soviet economy, bankingSystem, Gosbank monopoly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bankingSystem Context triple: [Soviet economy, bankingSystem, Gosbank monopoly]
-
A.
bankingModel
chosen
Indicates the financial or operational framework under which banking activities, services, and relationships are structured and conducted.
-
B.
bankingType
Indicates the category or model of banking relationship or services associated with an entity (e.g., retail, corporate, investment).
-
C.
hasBanking
Indicates that one entity provides or is associated with banking services or facilities for another entity.
-
D.
banking
Indicates that an entity provides or engages in financial services such as holding deposits, managing accounts, or facilitating monetary transactions for another entity.
-
E.
bank
Indicates that an entity provides financial services such as holding deposits, lending money, or managing financial transactions for another entity.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.